From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb@sources.redhat.com
Subject: gcc HEAD status with gdb
Date: Fri, 11 Jul 2003 16:32:00 -0000 [thread overview]
Message-ID: <200307111632.h6BGWYP0031001@duracef.shout.net> (raw)
FYI,
There are about 30 gdb regressions from gcc 3.3 to gcc HEAD.
This bug report explains about 12 of them:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11500
gcc HEAD just entered stage 2, which means they are about four months
away from branching. My goal is to have no regressions in the gdb test
suite for gcc HEAD before gcc-3_4-branch is cut.
Michael C
reply other threads:[~2003-07-11 16:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200307111632.h6BGWYP0031001@duracef.shout.net \
--to=mec@shout.net \
--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).