From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] mips-tdep.c: pseudo-register -> raw register sign extension
Date: Wed, 15 Dec 2010 20:54:00 -0000 [thread overview]
Message-ID: <20101215135352.0ba852ee@mesquite.lan> (raw)
In-Reply-To: <20101209162000.29cb4e3f@mesquite.lan>
On Thu, 9 Dec 2010 16:20:00 -0700
Kevin Buettner <kevinb@redhat.com> wrote:
> * mips-tdep.c (mips_pseudo_register_write): Sign extend 32-bit
> cooked values that are being transferred to 64-bit raw registers.
> (mips_pseudo_register_read): Revise to preserve symmetry with
> mips_pseudo_register_write().
Committed.
Kevin
prev parent reply other threads:[~2010-12-15 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 23:47 Kevin Buettner
2010-12-09 11:19 ` Mark Kettenis
2010-12-09 23:20 ` Kevin Buettner
2010-12-15 20:54 ` 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=20101215135352.0ba852ee@mesquite.lan \
--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