From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@cygnus.com, drow@mvista.com, eliz@is.elta.co.il
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] import drow dbxread.c fix to branch
Date: Wed, 03 Apr 2002 20:48:00 -0000 [thread overview]
Message-ID: <200204040448.g344m9L27264@duracef.shout.net> (raw)
Welcome back, Andrew!
Andrew Cagney writes:
> Fortunatly (for JimB), DanielJ found a fix for the problem and that has
> slowly been working its way into the branch.
Here is the current status from my perspective:
. DanielJ's fix is great for PR gdb/379 and PR gdb/380. It has been in
mainline for a couple of test cycles with no regressions. It's one of the
steps DanielJ took to reach his fabulous "NO FAIL" tree.
. I grabbed the patch and tested it on the 5.2 branch. It tests great
over there.
. I'm waiting for approval to commit to the branch. Then I can spin more
test results and produce another detailed "5.1.1 versus gdb_5_2-branch"
report.
. This fix does not fix PR gdb/381. gdb/381 is still happening in mainline.
I'm secretly hoping that DanielJ will take an interest in it.
. I am ambivalent about whether gdb/381 is a showstopper. On one hand:
any regression is bad and should be nailed down before a release.
On the other hand: gdb/381 happens only in gcc-3_1-branch and
gcc HEAD, which are not released. "Ambivalence" also translates to:
I'll be comfortable with whatever Andrew decides.
Michael C
next reply other threads:[~2002-04-04 4:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 20:48 Michael Elizabeth Chastain [this message]
2002-04-03 21:09 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2002-04-05 13:34 Michael Elizabeth Chastain
2002-04-04 18:17 Michael Elizabeth Chastain
2002-04-04 18:36 ` Daniel Jacobowitz
2002-04-04 19:35 ` Elena Zannoni
2002-04-05 13:10 ` Jim Blandy
2002-04-05 13:16 ` Daniel Jacobowitz
2002-04-04 8:37 Michael Elizabeth Chastain
2002-04-03 21:36 Michael Elizabeth Chastain
2002-04-03 22:01 ` Daniel Jacobowitz
2002-04-04 10:58 ` Andrew Cagney
2002-04-04 11:33 ` Elena Zannoni
2002-04-04 11:40 ` Daniel Jacobowitz
2002-04-04 12:15 ` Elena Zannoni
2002-04-04 12:24 ` Daniel Jacobowitz
2002-04-04 12:18 ` Andrew Cagney
2002-04-04 12:20 ` Daniel Berlin
2002-04-04 12:30 ` Andrew Cagney
2002-04-01 21:36 Michael Elizabeth Chastain
2002-04-01 21:43 ` Eli Zaretskii
2002-04-03 19:43 ` Andrew Cagney
2002-04-01 11:22 Michael Elizabeth Chastain
2002-04-01 20:49 ` Eli Zaretskii
2002-04-01 8:56 Michael Elizabeth Chastain
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=200204040448.g344m9L27264@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@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