From: Michael Elizabeth Chastain <mec@shout.net>
To: cgf@redhat.com, gdb@sources.redhat.com
Subject: Re: gcc HEAD bad stabs (?)
Date: Fri, 12 Sep 2003 22:24:00 -0000 [thread overview]
Message-ID: <200309122224.h8CMOSkI027465@duracef.shout.net> (raw)
cgf> "again"? When did it stop?
Okay, "again" is not quite what I meant to say. I really meant:
"once again, gcc HEAD has a new bug". I'm starting to expect 1-2
of these per week.
cgf> Things seem to be getting worse and worse.
They are. I'm opening bugs against gcc HEAD faster than the gcc
people are closing them. And I still have several regressions
left over from the April-June period when I wasn't around.
As far as I can see, the only feedback loop for gcc debug info
changes is me running the test suite. Ideas for improving this
welcomed.
Maybe I should set up a separate test bed and spin it
1-2 times per day with gcc HEAD, binutils 2.14, gdb 5.3.91.
Michael C
next reply other threads:[~2003-09-12 22:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 22:24 Michael Elizabeth Chastain [this message]
2003-09-13 0:01 ` Christopher Faylor
-- strict thread matches above, loose matches on Subject: below --
2003-09-13 0:40 Michael Elizabeth Chastain
2003-09-13 0:17 Michael Elizabeth Chastain
2003-09-13 0:36 ` Christopher Faylor
2003-09-12 18:33 Michael Elizabeth Chastain
2003-09-12 8:11 Michael Elizabeth Chastain
2003-09-12 14:33 ` Daniel Jacobowitz
2003-09-12 21:05 ` Christopher Faylor
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=200309122224.h8CMOSkI027465@duracef.shout.net \
--to=mec@shout.net \
--cc=cgf@redhat.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