From: Tom Rini <trini@ti.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Jianpeng Ma <majianpeng@gmail.com>,
Rusty Russell <rusty@rustcorp.com.au>, <tglx@linutronix.de>,
<x86@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: compile x86_64 waring
Date: Thu, 25 Jul 2013 08:17:17 -0400 [thread overview]
Message-ID: <51F1174D.2010105@ti.com> (raw)
In-Reply-To: <1374745288.29835.41.camel@x61.thuisdomein>
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.
--
Tom
next prev parent reply other threads:[~2013-07-25 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 11:56 compile x86_64 waring majianpeng
2013-07-24 21:05 ` Paul Bolle
2013-07-24 23:22 ` Tom Rini
2013-07-25 8:53 ` Paul Bolle
2013-07-25 9:41 ` Paul Bolle
2013-07-25 12:17 ` Tom Rini [this message]
2013-10-30 13:04 ` Leon Gorge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51F1174D.2010105@ti.com \
--to=trini@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=majianpeng@gmail.com \
--cc=pebolle@tiscali.nl \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox