From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] rl78-tdep.c: Make PC a pseudo-register
Date: Fri, 16 Aug 2013 04:31:00 -0000 [thread overview]
Message-ID: <20130815213147.04321a4b@redhat.com> (raw)
In-Reply-To: <20130808205554.070f72ce@redhat.com>
On Thu, 8 Aug 2013 20:55:54 -0700
Kevin Buettner <kevinb@redhat.com> wrote:
> * rl78-tdep.c (RL78_RAW_PC_REGNUM): New enum.
> (RL78_PC_REGNUM): Move to list of pseudo-register enums.
> (rl78_register_type, rl78_register_name, rl78_register_reggroup_p):
> Update to account for fact that PC is now a pseudo-register.
> (rl78_pseudo_register_write, rl78_pseudo_register_read): Add
> cases for RL78_PC_REGNUM.
Committed (with Joel's suggested changes).
Thanks again to Joel for looking it over.
Kevin
prev parent reply other threads:[~2013-08-16 4:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 3:56 Kevin Buettner
2013-08-14 14:04 ` Joel Brobecker
2013-08-15 4:34 ` Kevin Buettner
2013-08-16 4:31 ` Kevin Buettner [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=20130815213147.04321a4b@redhat.com \
--to=kevinb@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).