From: Robert Lipe <robertlipe@usa.net>
To: egcs@egcs.cygnus.com
Cc: bje@cygnus.com
Subject: Re: dwarf-2 problem on cc1
Date: Wed, 30 Jun 1999 15:43:00 -0000 [thread overview]
Message-ID: <19990613001932.A23053@rjlhome.sco.com> (raw)
Message-ID: <19990630154300.yQfqAH4c748f9b0TrnQEfaFOK3fOejY9SCElKF_ZLfA@z> (raw)
In-Reply-To: <19990612234841.A22906@rjlhome.sco.com>
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
next prev parent reply other threads:[~1999-06-30 15:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-12 18:01 Robert Lipe
1999-06-12 21:49 ` Robert Lipe
1999-06-12 22:19 ` Robert Lipe [this message]
1999-06-12 23:12 ` Jeffrey A Law
1999-06-13 9:46 ` Robert Lipe
1999-06-14 5:46 ` Ben Elliston
1999-06-14 10:59 ` Jeffrey A Law
1999-06-30 15:43 ` Jeffrey A Law
1999-06-30 15:43 ` Ben Elliston
1999-06-30 15:43 ` Robert Lipe
1999-06-30 15:43 ` Jeffrey A Law
1999-06-30 15:43 ` Robert Lipe
1999-06-30 15:43 ` Robert Lipe
1999-06-30 15:43 ` Robert Lipe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19990613001932.A23053@rjlhome.sco.com \
--to=robertlipe@usa.net \
--cc=bje@cygnus.com \
--cc=egcs@egcs.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).