Bug#624354: Processed: Re: Bug#624354: ./xpcshell: error while loading shared libraries: ./libxul.so: R_PPC_REL24 relocation at 0x0f9f0148 for symbol `_restgpr_29_x' out of range
- To: Mike Hommey <mh@glandium.org>
- Cc: Michel Dänzer <daenzer@debian.org>, Matthias Klose <doko@debian.org>, 624354@bugs.debian.org, Cyril Brulebois <kibi@debian.org>, debian-powerpc@lists.debian.org
- Subject: Bug#624354: Processed: Re: Bug#624354: ./xpcshell: error while loading shared libraries: ./libxul.so: R_PPC_REL24 relocation at 0x0f9f0148 for symbol `_restgpr_29_x' out of range
- From: Gabriel Paubert <paubert@iram.es>
- Date: Thu, 28 Apr 2011 14:17:15 +0200
- Message-id: <20110428121715.GA5336@iram.es>
- Reply-to: Gabriel Paubert <paubert@iram.es>, 624354@bugs.debian.org
- In-reply-to: <20110428101054.GA9846@glandium.org>
- References: <20110428081500.GA5212@glandium.org> <20110428084507.GA5980@glandium.org> <1303982255.5633.218.camel@thor.local> <20110428092506.GA7806@glandium.org> <20110428093216.GB7806@glandium.org> <20110428094048.GA8307@glandium.org> <20110428095518.GA8610@glandium.org> <1303984864.5633.229.camel@thor.local> <20110428100442.GA9729@glandium.org> <20110428101054.GA9846@glandium.org>
On Thu, Apr 28, 2011 at 12:10:54PM +0200, Mike Hommey wrote:
> On Thu, Apr 28, 2011 at 12:04:42PM +0200, Mike Hommey wrote:
> > Let me write it again:
> > - The R_PPC_REL24 relocations are all over libxul.so on objects that are
> > built -fPIC.
> > - libcrmf.a is also linked into libxul.so, and it also contains
> > R_PPC_REL24 relocations, but all the objects it contains are built
> > -fPIC.
>
> And this is a -Os bug, apparently. Building with -O2 doesn't seem to
> yield these relocations.
That's because the out-of-line prologue/epilogue register save and
restore functions are only used at -Os (they save size).
Now I believe, but don't quote me on that, that the linker
should insert a copy of these functions in every shared library
since these functions have non standard linkage and probably
would not survive crossing shared library boundaries.
I can see a bug if the shared library text size is above
32M or so (needs several copies of these functions), but
I don't think the libraries are that big.
But I may be completely wrong on the last 2 paragraphs.
Regards,
Gabriel
Reply to: