From: Pedro Alves <palves@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] rl78: Rearrange order in which registers are displayed
Date: Tue, 14 Feb 2012 18:54:00 -0000 [thread overview]
Message-ID: <4F3AADA3.6050509@redhat.com> (raw)
In-Reply-To: <20120209171537.20c1c6b1@mesquite.lan>
On 02/10/2012 12:15 AM, Kevin Buettner wrote:
> The patch below uses register groups to shorten the list of registers
> displayed when "info registers" is used. It adds some pseudo registers
> and rearranges others so that the banked registers are displayed at
> the end for "info all-registers". The register order from 0 to NREGS
> stays the same.
>
> This change was requested by Renesas. They wanted the more useful and
> important registers displayed earlier on for "info all-registers".
>
> I considered writing a custom method for printing registers, but it
> seems that this approach has fallen out of favor these days. Also, I
> would guess that the custom approach might not be compatible with MI
> enabled clients.
>
> Comments?
FWIW, looks fine to me.
> +/* Implement the `register_sim_regno' gdbarch method. */
> +
> +static int
> +rl78_register_sim_regno(struct gdbarch *gdbarch, int regnum)
Missing space before parens.
--
Pedro Alves
next prev parent reply other threads:[~2012-02-14 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 0:16 Kevin Buettner
2012-02-14 18:54 ` Pedro Alves [this message]
2012-02-14 20:44 ` Kevin Buettner
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=4F3AADA3.6050509@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.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