[lkml]   [2012]   [Jul]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: linux-next: build failure after merge of the final tree
On Thu, Jul 05, 2012 at 06:33:45PM +1000, Stephen Rothwell wrote:
> powerpc64-linux-ld: drivers/built-in.o: In function `.gpiochip_is_requested':
> (.text+0x4): sibling call optimization to `_savegpr0_29' does not allow automatic multiple TOCs; recompile with -mminimal-toc or -fno-optimize-sibling-calls, or make `_savegpr0_29' extern
> I got more than 60000 of these messages before I killed the link. :-( I
> am not sure what has changed to do this, but it may have been masked for
> the past few releases due to other linking problems.

Let me guess. You're using bleeding edge gcc but not binutils.

a) Recent gcc has fixed prologue and epilogue generation which now
properly makes use of out-of-line register save and restore
functions when compiling with -Os.
b) Recent ld doesn't emit out-of-line save/restore function for ld -r,
but yours does. You need my 2012-06-22 patch.
c) Kernel uses ld -r for packaging.

(b) and (c) together mean you get a definition for _savegpr0_29 munged
together with other functions. That's bad. If _savegpr0_29 wasn't
emitted until the final link stage then it would be in a code section
containing just save/restore functions. ld will analyse that section
and notice the absense of toc relocations; functions therein don't
use the toc and can thus be called from any toc group without needing
a toc adjusting stub. In your case _savegpr0_29 is in a section that
has toc relocations (from normal compiled code), so ld decides that
any function in that section must have a proper value for the toc
register. But calls to _savegpr0_29 don't have a following nop to
overwrite with a toc restore insn, hence the ld error.

Score another black mark for ld -r.

Alan Modra
Australia Development Lab, IBM

 \ /
  Last update: 2012-07-05 12:21    [W:0.052 / U:19.648 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site