This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Using binutils-2.12.1 on sparc64-sun-solaris2.8 to build gcc-3.1 results in relocation errors


On Mon, Jul 15, 2002 at 07:44:14PM -0700, David S. Miller wrote:
>    From: Alan Modra <amodra@bigpond.net.au>
>    Date: Tue, 16 Jul 2002 12:10:12 +0930
> 
>    On Mon, Jul 15, 2002 at 12:45:33PM -0500, Dana, Eric wrote:
>    > When building some of our 64-bit libraries in C++, we are seeing
>    > R_SPARC_DISP32 errors:
>    
>    Please try current binutils CVS.  If the problem isn't fixed there,
>    now would be the time to shout about it.  We're about to release 2.13.
> 
> Actually this looks like some kind of code-model error.
> There should not be any R_SPARC_DISP32 relocations generated
> as no "call" instruction based function invocations should
> be emitted with Solaris's default code model.
> 
> "Call" is the only way R_SPARC_DISP32 relocations can be
> emitted.

No, call generates R_SPARC_WDISP32. R_SPARC_DISP32 is generated by
something like .word %r_disp32(foo + 12345).

%r_disp32() is emitted by gcc for the .eh_frame section (only when using
GNU ld, since Solaris ld has broken support for misaligned PC relative
relocs).
Are your 64-bit libraries bigger than 2GB?

	Jakub


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]