* GOT entries 0 with gcc2.95.3/binutils2.14 but properly relocated with gcc4.1.1/binutils16.5
@ 2007-10-25 13:28 Roland Puntaier
2007-10-26 11:27 ` Alan Modra
0 siblings, 1 reply; 2+ messages in thread
From: Roland Puntaier @ 2007-10-25 13:28 UTC (permalink / raw)
To: binutils
Hello,
when linking blcyclic.o into bl.out
.got entries stay 0 and R_386_GLOB_DAT relocations are issued for
2.95.3/binutils2.14,
while .got entries get filled and R_386_RELATIVE relocations get issued
with GCC 4.1.1/binutils 16.5.
Is there a way to make the former do what the latter does?
Thanks for any hint.
Roland
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: GOT entries 0 with gcc2.95.3/binutils2.14 but properly relocated with gcc4.1.1/binutils16.5
2007-10-25 13:28 GOT entries 0 with gcc2.95.3/binutils2.14 but properly relocated with gcc4.1.1/binutils16.5 Roland Puntaier
@ 2007-10-26 11:27 ` Alan Modra
0 siblings, 0 replies; 2+ messages in thread
From: Alan Modra @ 2007-10-26 11:27 UTC (permalink / raw)
To: Roland Puntaier; +Cc: binutils
On Thu, Oct 25, 2007 at 02:38:22PM +0200, Roland Puntaier wrote:
> when linking blcyclic.o into bl.out
> .got entries stay 0 and R_386_GLOB_DAT relocations are issued for
> 2.95.3/binutils2.14,
> while .got entries get filled and R_386_RELATIVE relocations get issued
> with GCC 4.1.1/binutils 16.5.
>
> Is there a way to make the former do what the latter does?
Of course. You have the source!
--
Alan Modra
Australia Development Lab, IBM
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-10-26 6:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-10-25 13:28 GOT entries 0 with gcc2.95.3/binutils2.14 but properly relocated with gcc4.1.1/binutils16.5 Roland Puntaier
2007-10-26 11:27 ` Alan Modra
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 read-only IMAP folder(s) and NNTP newsgroup(s).