summaryrefslogtreecommitdiffstats
path: root/kernel/module.c
diff options
context:
space:
mode:
authorPaul Gortmaker <paul.gortmaker@windriver.com>2015-04-20 02:50:40 +0200
committerRusty Russell <rusty@rustcorp.com.au>2015-04-22 10:01:34 +0200
commit4a3893d069b788f3570c19c12d9e986e8e15870f (patch)
treef2b4c93e1239befe1acc257b683bbba6c1ef8ff1 /kernel/module.c
parentmodpost: expand pattern matching to support substring matches (diff)
downloadlinux-4a3893d069b788f3570c19c12d9e986e8e15870f.tar.xz
linux-4a3893d069b788f3570c19c12d9e986e8e15870f.zip
modpost: don't emit section mismatch warnings for compiler optimizations
Currently an allyesconfig build [gcc-4.9.1] can generate the following: WARNING: vmlinux.o(.text.unlikely+0x3864): Section mismatch in reference from the function cpumask_empty.constprop.3() to the variable .init.data:nmi_ipi_mask which comes from the cpumask_empty usage in arch/x86/kernel/nmi_selftest.c. Normally we would not see a symbol entry for cpumask_empty since it is: static inline bool cpumask_empty(const struct cpumask *srcp) however in this case, the variant of the symbol gets emitted when GCC does constant propagation optimization. Fix things up so that any locally optimized constprop variants don't warn when accessing variables that live in the __init sections. Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Diffstat (limited to 'kernel/module.c')
0 files changed, 0 insertions, 0 deletions