From: Segher Boessenkool <segher@kernel.crashing.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>,
Andrew Morton <akpm@linux-foundation.org>,
amodra@bigpond.net.au
Subject: Re: Problems with allyesconfig kernel build
Date: Tue, 23 Oct 2007 11:09:04 +0200 [thread overview]
Message-ID: <abdbca68b7265f0722eca787b16b4dae@kernel.crashing.org> (raw)
In-Reply-To: <20071023140231.12698d1c.sfr@canb.auug.org.au>
> This was first noted with the -mm tree, but has now migrated into
> Linus'
> tree. An allyesconfig build dies in the link stage like this:
>
> /usr/bin/ld: arch/powerpc/kernel/head_64.o(.text+0x80c8): sibling call
> optimization to `.text.init.refok' does not allow automatic multiple
> TOCs; recompile with -mminimal-toc or -fno-optimize-sibling-calls, or
> make `.text.init.refok' extern
> /usr/bin/ld: arch/powerpc/kernel/head_64.o(.text+0x8160): sibling call
> optimization to `.text.init.refok' does not allow automatic multiple
> TOCs; recompile with -mminimal-toc or -fno-optimize-sibling-calls, or
> make `.text.init.refok' extern
> /usr/bin/ld: arch/powerpc/kernel/head_64.o(.text+0x81c4): sibling call
> optimization to `.text.init.refok' does not allow automatic multiple
> TOCs; recompile with -mminimal-toc or -fno-optimize-sibling-calls, or
> make `.text.init.refok' extern
> /usr/bin/ld: final link failed: Bad value
I just tried, and it works fine for me.
> Intuiting the obvious, I changed all the _INIT_STATIC and _INIT_GLOBAL
> uses in head_64.S back to _STATIC and _GLOBAL (which just moves the
> code
> from .text.init.refok to .text). Now the linker segfaults instead.
> :-)
Tried that, too, and no segfault, everything happy.
> $ ld --version
> GNU ld (GNU Binutils for Debian) 2.18
I'm using CVS HEAD of binutils. Could you try that, with the same
GCC version you are currently using? Just to narrow things down...
Segher
next prev parent reply other threads:[~2007-10-23 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 4:02 Problems with allyesconfig kernel build Stephen Rothwell
2007-10-23 4:07 ` Stephen Rothwell
2007-10-23 4:18 ` Andrew Morton
2007-10-23 4:47 ` Stephen Rothwell
2007-10-23 9:09 ` Segher Boessenkool [this message]
2007-10-23 10:19 ` Alan Modra
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=abdbca68b7265f0722eca787b16b4dae@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=amodra@bigpond.net.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).