From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: deuling@de.ibm.com (Markus Deuling)
Cc: gdb-patches@sourceware.org (GDB Patches),
brobecker@adacore.com (Joel Brobecker),
drow@false.org (Daniel Jacobowitz),
eliz@gnu.org (Eli Zaretskii),
mark.kettenis@xs4all.nl (Mark Kettenis)
Subject: Re: [rfc] [00/15] Add gdbarch to register_name callback
Date: Thu, 01 Nov 2007 15:22:00 -0000 [thread overview]
Message-ID: <200711011522.lA1FM1eN017802@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <47298E06.6090108@de.ibm.com> from "Markus Deuling" at Nov 01, 2007 09:27:50 AM
Markus Deuling wrote:
> I attached a new patch which is nearly a merge of the last 15 patches. I included the trivial replacements
> of current_gdbarch (by gdbarch, get_frame_arch or get_regcache_arch). The patch does not contain the non-trivial
> replacements like dissolving macros etc anymore. I'll follow-up on that after this on is committed.
Thanks for re-working the patch.
> > Otherwise, the changes look fine to me.
>
> I also changed "M" to "m" for register_name and introduced a new default_register_name function that just returns NULL.
Ah, this was not quite what I had in mind, sorry. I do not think
it makes sense to have a "default_register_name" -- every gdbarch
*must* provide a register_name function. I was thinking of something
along the lines of
m:const char *:register_name:int regnr:regnr::0
This will cause verify_gdbarch to abort if no register_name is
registered.
Could you make that change and re-submit? The rest of the
patch is OK.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2007-11-01 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 10:47 Markus Deuling
2007-10-31 23:46 ` Ulrich Weigand
2007-11-01 8:30 ` Markus Deuling
2007-11-01 15:22 ` Ulrich Weigand [this message]
2007-11-02 8:09 ` Markus Deuling
2007-11-02 14:28 ` 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=200711011522.lA1FM1eN017802@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=brobecker@adacore.com \
--cc=deuling@de.ibm.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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