This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: fixes for Darwin/x86
On Nov 30, 2005, at 2:44 PM, Andreas Tobler wrote:
Stuart Hastings wrote:
We've been neglecting the Darwin/x86 port. Mea culpa.
My Darwin/x86 box is currently running version 8F1111 of OS X,
upgraded ep
Hm, quite a big step between ppc and x86, I have 8F46 on ppc vs.
your 8F1111 on x86 :)
Newer means newer; IMHO, that's not quite the same as "better." ;-)
with cctools v590.20 (cctools means assembler, static and dynamic
linkers, etc).
Does this v590.20 fix an ld bug (known to Geoffk, 4226076) and if
so, will it be available soon ?
I checked the Radar ("linking 25x slower when linking against a dylib
built with -single_module"); sorry, no. :-(
The linker change I'm referencing just eliminates a warning; the
silence "fixes" about 70 DejaGnu FAILs. I mentioned it because it
makes a significant difference in DejaGnu testing; nothing in the
patch depends upon the new linker. If someome (like you) was to
build GCC on a Darwin/x86 box with the old linker, you would see
those 70-odd failures, thus I'm obliged to credit the linker with
those PASSes. My patch doesn't address them at all.
IIRC, the warning was due to a symbol collision between a global
symbol and a dynamic library; e.g. DejaGnu now supplies its own
version of 'memset' for many tests, and the Darwin linker used to
warn about it colliding with another memset in some Apple dylib.
stuart