From: Michael Elizabeth Chastain <mec@shout.net>
To: carlton@math.stanford.edu, gdb@sources.redhat.com
Cc: drow@mvista.com
Subject: Re: GCC, stabs, mangled names
Date: Tue, 11 Mar 2003 05:55:00 -0000 [thread overview]
Message-ID: <200303110555.h2B5t5K17176@duracef.shout.net> (raw)
Hi David,
> Is there a problem with gcc -gstabs+ and mangled names in recent
> GCC's?
What do you mean by "recent GCC's"?
gcc 3.2.2 and gcc gcc-3_2-branch are fine.
I'm getting dozens of new regressions with gcc HEAD -gstabs+,
regressions from 2003-02-28 to 2003-03-08.
gcc gcc-3_3-branch has a non-stabs regression where programs that
include standard header files don't compile (pr gcc/10018).
I suspect that most of the people who test gcc test a built,
non-installed version, because it shows up quick when I install
gcc and set my $PATH to use it.
Michael C
next reply other threads:[~2003-03-11 5:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 5:55 Michael Elizabeth Chastain [this message]
2003-03-11 17:06 ` David Carlton
-- strict thread matches above, loose matches on Subject: below --
2003-03-11 17:24 Michael Elizabeth Chastain
2003-03-11 6:07 Michael Elizabeth Chastain
2003-03-11 20:33 ` David Carlton
2003-03-11 0:53 David Carlton
2003-03-11 0:57 ` Daniel Jacobowitz
2003-03-11 1:20 ` David Carlton
2003-03-11 1:24 ` Daniel Jacobowitz
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=200303110555.h2B5t5K17176@duracef.shout.net \
--to=mec@shout.net \
--cc=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.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).