Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: Remove code handling old ARM aliases from GDB
Date: Fri, 06 May 2011 00:23:00 -0000	[thread overview]
Message-ID: <20110506002328.GC2568@adacore.com> (raw)
In-Reply-To: <alpine.BSF.2.00.1105051839200.67473@dair.pair.com>

> As having introduced this, you're on the hook to investigate and
> rectify.  Another option to those I mentioned is to xfail or
> kfailing the failing tests.  Please.

I've tried to understand the problem, and it seems to me that Joseph's
position is entirely reasonable in this case. He has effectively
introduced new tests that happen to fail in the arm-elf case, is that
correct? If they fail on arm-elf, someone who cares about this platform
should investigate them and determine whether to fix them, or whether
they are a sim/gdb problem (kfail), or a problem from an external
dependency (xfail).

-- 
Joel


  parent reply	other threads:[~2011-05-06  0:23 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
2011-05-05 23:52           ` Joseph S. Myers
2011-05-06  0:23           ` Joel Brobecker [this message]
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=20110506002328.GC2568@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hp@bitrange.com \
    --cc=joseph@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