bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/7023] ld is unable to link 32 bit libffi.so on gcc mainline: Mem


From: ro at TechFak dot Uni-Bielefeld dot DE
Subject: [Bug ld/7023] ld is unable to link 32 bit libffi.so on gcc mainline: Memory exhausted
Date: 13 Nov 2008 19:54:27 -0000

------- Additional Comments From ro at TechFak dot Uni-Bielefeld dot DE  
2008-11-13 19:54 -------
Subject: Re:  ld is unable to link 32 bit libffi.so on gcc mainline: Memory 
exhausted

ebotcazou at gcc dot gnu dot org writes:

> > the last half-sentence about memory corruption: no details, no PR or
> > whatever.
> 
> On purpose, the GCC manual is not the right place for that.

Agreed: I'll have to lookup the details myself.

> > Although the bugs seem to be easily fixed  Besides, breakage wide into the
> > bootstraps seems like a poor way to convey that information ;-)
> 
> You'll get a non-working toolchain in all cases...

I'm not sure yet: the GCC PRs can be worked around by using
--disable-symvers for now, but that should be automatic.  This PR can (and
should) be fixed both in Sun as and GNU ld, and PR ld/7027 should be worked
around in GNU ld either, just as in the similar 32-bit case.

> > My change needs to be tested with both Sun ld and GNU ld since the
> > inclusion of gcc/config/i386/t-crtstuff will become conditional upon a link
> > test, and I need to test all paths: older/broken Sun ld, new/fixed Sun ld
> > and GNU ld.  And for the GNU ld case (which I've not tried in a long time
> > if at all) I need a baseline without my change.
> 
> Use GNU as.

Indeed: that's what I'll do for the moment.

        Rainer


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=7023

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]