From: Michael Chastain <mec.gnu@mindspring.com>
To: zack@codesourcery.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: testsuite fixes for bleeding edge gcc
Date: Thu, 14 Oct 2004 18:55:00 -0000 [thread overview]
Message-ID: <416ECB94.nail14E11I0TO@mindspring.com> (raw)
In-Reply-To: <87y8i9kzh0.fsf@codesourcery.com>
> whether my GCC changes worked.
Ah. That is a good reason for me to keep up maintenance on the
6.2 branch, if it happens often enough. Just because we don't
release from the branch doesn't mean it's useless.
Also if you are doing before-and-after comparisons with gdb,
watch out for some tests that are unstable from run to run.
http://sources.redhat.com/ml/gdb-testers
... and search for particular test names. Or just google the
test names.
> Would be nice to get gdb.mi/gdb701 fixed in HEAD though.
Yeah. Andrew or I have to pick up that little nit.
Michael
next prev parent reply other threads:[~2004-10-14 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 7:53 Zack Weinberg
2004-10-14 12:04 ` Michael Chastain
2004-10-14 16:59 ` Zack Weinberg
2004-10-14 18:55 ` Michael Chastain [this message]
2004-10-14 21:32 ` Zack Weinberg
2004-10-14 19:14 ` Andrew Cagney
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=416ECB94.nail14E11I0TO@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=gdb-patches@sources.redhat.com \
--cc=zack@codesourcery.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