From: Joel Brobecker <brobecker@adacore.com>
To: Daniel Jacobowitz <dan@codesourcery.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>,
gdb-patches@sourceware.org, gdb@sourceware.org,
vladimir@codesourcery.com
Subject: Re: [patch] Re: -data-list-register-names regression?
Date: Wed, 17 Mar 2010 22:59:00 -0000 [thread overview]
Message-ID: <20100317225950.GH3830@adacore.com> (raw)
In-Reply-To: <20100317223740.GP9310@caradoc.them.org>
> > Tested on powerpc-linux. Thoughts on whether we should this?
>
> I like this patch, and think we should use it. The IDE should be
> re-fetching the register names, but we don't need to be mean about it :-)
Ditto. Do we want it for 7.1?
--
Joel
next prev parent reply other threads:[~2010-03-17 22:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201003171345.44000.vladimir@codesourcery.com>
2010-03-17 21:38 ` Ulrich Weigand
2010-03-17 22:37 ` Daniel Jacobowitz
2010-03-17 22:59 ` Joel Brobecker [this message]
2010-03-18 4:44 ` Dave Korn
2010-03-18 13:28 ` Ulrich Weigand
2010-03-18 13:55 ` Joel Brobecker
2010-03-18 15:53 ` Ulrich Weigand
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=20100317225950.GH3830@adacore.com \
--to=brobecker@adacore.com \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=uweigand@de.ibm.com \
--cc=vladimir@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