Re: compile x86_64 waring

[Leon Gorge]

Tom Rini <trini <at> ti.com> writes:

> 
> On 07/25/2013 05:41 AM, Paul Bolle wrote:
> > Tom,
> > 
> > On Thu, 2013-07-25 at 10:53 +0200, Paul Bolle wrote:
> >> But I've just pulled top-of-tree Linus, ie commit 07bc9dc1b0
> >> ("git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc'"). I'll
> >> try to build that and I 'll send you my .config if this all is still
> >> triggered.
> > 
> > It is still seen with "make bzImage" at v3.11-rc2-185-g07bc9dc (current
> > Linus' tip-of-tree). I get, in summary:
> >     WARNING: arch/x86/mm/built-in.o(.text.unlikely+0xbf2): Section
mismatch in reference from the
> function __node_set.constprop.0() to the variable .init.data:numa_nodes_parsed
> >     WARNING: arch/x86/built-in.o(.text.unlikely+0x140e): Section
mismatch in reference from the
> function __node_set.constprop.0() to the variable .init.data:numa_nodes_parsed
> >     WARNING: vmlinux.o(.text.unlikely+0x1444): Section mismatch in
reference from the function
> __node_set.constprop.0() to the variable .init.data:numa_nodes_parsed
> > 
> > But it is all the same thing (the issue apparently just repeat itself
> > when arch/x86/mm/built-in.o is merged into arch/x86/built-in.o, and
> > again when arch/x86/built-in.o is merged into vmlinux.o).
> 
> OK, thanks.  I just posted a patch that fixes the warning here.  The
> problem is that __node_set wasn't being inlined by the compiler, so you
> have the section mis-match above.
> 


Hello,

I'm just facing the same warning compiling 3.11.4 and 3.11.6 and i wondered
wether your patch shouldn't already be included?

The config was being used with practically every third or fourth
kernel-release since 3.2.something (with adjustments from time to time).

I've re-done the NUMA-related config with 3.7 and didn't get any warnings
until now. Shall i post my config?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/