From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Remove code handling old ARM aliases from GDB
Date: Thu, 05 May 2011 23:19:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1105052313170.20285@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.BSF.2.00.1105051839200.67473@dair.pair.com>
On Thu, 5 May 2011, Hans-Peter Nilsson wrote:
> Splitting of hairs, choice of words. I guess we have to
> disagree on the words, but I'm sure we can agree that running
> the tests does exit with an error after, but didn't before your
> changes.
sim tests on their own, yes - I just consider this to be an *improvement*
(better testsuite coverage, exit status more accurately reflecting the
existence of defects). I think of sim as part of GDB, and I've never seen
the gdb testsuite anywhere near to having completely clean results for any
target.
> As having introduced this, you're on the hook to investigate and
> rectify.
I'm not expert on GDB policies. Where is this documented and would this
apply to the case I described of tests for complex numbers ABI handling,
which I consider exactly analogous? I don't believe this would apply
under GCC practice, as it's not a regression but (effectively) a new test.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2011-05-05 23:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 19:01 Joseph S. Myers
2011-05-04 19:21 ` Mark Kettenis
2011-05-04 19:23 ` Pedro Alves
2011-05-04 19:24 ` Pedro Alves
2011-05-05 13:21 ` Hans-Peter Nilsson
2011-05-05 13:47 ` Hans-Peter Nilsson
2011-05-05 14:34 ` Joseph S. Myers
2011-05-05 22:11 ` Hans-Peter Nilsson
2011-05-05 22:34 ` Joseph S. Myers
2011-05-05 23:06 ` Hans-Peter Nilsson
2011-05-05 23:19 ` Joseph S. Myers [this message]
2011-05-05 23:52 ` Joseph S. Myers
2011-05-06 0:23 ` Joel Brobecker
2011-05-06 3:00 ` Hans-Peter Nilsson
[not found] ` <Pine.LNX.4.64.1105052349190.20285@digraph.polyomino.org.uk>
2011-05-09 4:53 ` Hans-Peter Nilsson
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=Pine.LNX.4.64.1105052313170.20285@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=hp@bitrange.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