From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: deuling@de.ibm.com (Markus Deuling)
Cc: gdb-patches@sourceware.org (GDB Patches)
Subject: Re: [rfc] [01/15] Add gdbarch to register_name callback (prep)
Date: Wed, 31 Oct 2007 22:11:00 -0000 [thread overview]
Message-ID: <200710312154.l9VLsldG023515@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <47285CC8.80902@de.ibm.com> from "Markus Deuling" at Oct 31, 2007 11:45:28 AM
Markus Deuling wrote:
> -f:const char *:register_name:int regnr:regnr
> +M:const char *:register_name:int regnr:regnr
You should be using "m" instead of "M". The latter will allow
targets to not provide a gdbarch_register_name callback, which
doesn't make much sense -- this routine should remain required.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
prev parent reply other threads:[~2007-10-31 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 10:48 Markus Deuling
2007-10-31 22:11 ` Ulrich Weigand [this message]
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=200710312154.l9VLsldG023515@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=deuling@de.ibm.com \
--cc=gdb-patches@sourceware.org \
/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