Bootstrap is STILL broken...
Andrew Pinski
pinskia@physics.uc.edu
Thu Apr 1 00:07:00 GMT 2004
On Mar 31, 2004, at 18:56, Dale Johannesen wrote:
>
> (I am not a Darwin maintainer, but OK. Perhaps I should be at this
> point?)
> I do not think this is the right general approach to the problem, as I
> said, but
> in the interests of getting bootstrap going I'll go along with it.
>
> These routines are the same ones that have been used in Apple's gcc
> for years,
> so they're technically OK. I've verified that they were written at
> Apple and we
> are willing to contribute them, so there's no legal problem.
In reality, it is the right approach as you can now link code generated
by Apple's
compiler and the FSF compiler which you could not do always before.
Changing libiberty
to be bootstrap able will not fix that problem, just the bootstrap
problem.
Also technically the current patch in Apple's compiler is wrong as the
functions are
private extern and only are included in the shared library so they are
not exported to
C++ code so C++ code now will not link with Apple's 3.5 based compiler.
Thanks,
Andrew Pinski
More information about the Gcc-patches
mailing list