This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: dwarf-2 problem on cc1
Ben, how would you and Jeff about using a post 2.13 autoconf for 2.95?
> Sure enough, if I blast libiberty and rebuild it with the freshly built
> GCC, and relink cc1 with that libiberty this issue goes away.
As crazy as all this sounds, this is indeed triggered by an old version
of autoconf. If I regenerate libiberty/configure and nuke the caches,
cc1 no longer contains the dwarf records that sends it over the edge.
I was really suprised that the third-stage cc1 contained references to
memset and memcpy but apparently there was a use somewhere that just
couldn't be inlined so we get into the weirdness of mixing native and
gcc objects.
According to autoconf/ChangeLog, 2.13 was released on 1/5. The patch in
question (and it was Joerne, not Richard. Sorry.) was installed on 1/9.
The patch was actually submitted in October.
I won't hard-sell you on the idea since some other changes I made in
EGCS reduced this from link failure during bootstrap to "merely" making
cc1 hard to debug.
RJL