From: Steven Rostedt <rostedt@goodmis.org>
To: nick <xerofoify@gmail.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, peterz@infradead.org, jiang.liu@linux.intel.com,
oleg@redhat.com, luto@amacapital.net, bp@suse.de,
linux-kernel@vger.kernel.org
Subject: Re: Linker Issues with built-in.o on my machine for x86
Date: Sun, 11 Jan 2015 16:54:03 -0500 [thread overview]
Message-ID: <20150111165403.1069bc66@gandalf.local.home> (raw)
In-Reply-To: <54B2DF76.8020200@gmail.com>
On Sun, 11 Jan 2015 15:39:18 -0500
nick <xerofoify@gmail.com> wrote:
> Greetings x86 Maintainers.
> I am getting a linker error as of today on a up to date git tree of linus's on my x86 machine.
> Below this message is the linker message I am getting.
> WARNING: arch/x86/kernel/built-in.o(.text.unlikely+0x1204): Section mismatch in reference from the function cpumask_empty.constprop.3() to the variable .init.data:nmi_ipi_mask
> The function cpumask_empty.constprop.3() references
> the variable __initdata nmi_ipi_mask.
> This is often because cpumask_empty.constprop.3 lacks a __initdata
Hmm, I bet it had something to do with some sort of gcc optimization,
and is mostly harmless.
> annotation or the annotation of nmi_ipi_mask is wrong.
What gcc are you using and can you send your .config.
remote_ipi() (which is annotated as __init), calls cpumask_empty()
(a static inlined function) with to_cpumask(nmi_ipi_mask). There's
nothing wrong here. I don't see anyway that cpumask_empty() could use
nmi_ipi_mask after boot up.
Seeing that it's not cpumask_empty(), but cpumask_empty.constprop.3
tells me that gcc probably created some function from the static inline
function of cpumask_empty() and that causes the section mismatch test
to give a false error.
If anything should be fixed here, it is to find a way to fix the section
mismatch test from reporting bogus errors like this.
-- Steve
parent reply other threads:[~2015-01-11 21:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <54B2DF76.8020200@gmail.com>]
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=20150111165403.1069bc66@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=jiang.liu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xerofoify@gmail.com \
/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
all inboxes | Powered by JetHome®