From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, gdb@sources.redhat.com
Subject: Re: GCC 3.4 vs GDB 6.1
Date: Thu, 08 Jan 2004 21:24:00 -0000 [thread overview]
Message-ID: <20040108212404.4BE1A4B35A@berman.michael-chastain.com> (raw)
> (kind of a bit late but ...)
> Are there any "bugs" GDB would like to see fixed in GCC 3.4?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12267
[3.4 regression] function-at-a-time generates stabs in bad order
This imparirs stabs+ support significantly.
Anonymous unions are another regression area.
I have "compare by gcc" tables but I haven't analyzed them yet.
This one bug causes so many problems that it's hard to look at
other stabs+ problems.
Grossly, there are about 27 new FAILS with gcc HEAD -gdwarf-2
versus gcc 3.3.2 -gdwarf-2, and about 28 new FAILS with gcc HEAD
-gstabs+ versus gcc 3.3.2 -gstabs+.
Michael C
next reply other threads:[~2004-01-08 21:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 21:24 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-08 20:30 Andrew Cagney
2004-01-08 20:33 ` Daniel Jacobowitz
2004-01-09 8:57 ` Eli Zaretskii
2004-01-09 14:36 ` Daniel Jacobowitz
2004-01-10 11:54 ` Eli Zaretskii
2004-01-10 16:34 ` 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=20040108212404.4BE1A4B35A@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--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