From: Kevin Buettner <kevinb@redhat.com>
To: Jim Blandy <jimb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [ppc64-linux]: correctly compute u-area register offsets
Date: Tue, 10 Jun 2003 16:32:00 -0000 [thread overview]
Message-ID: <1030610163241.ZM21700@localhost.localdomain> (raw)
In-Reply-To: Jim Blandy <jimb@redhat.com> "[ppc64-linux]: correctly compute u-area register offsets" (Jun 10, 11:25am)
On Jun 10, 11:25am, Jim Blandy wrote:
> This patch contains all my fixes to ppc_register_u_addr to date; I
> think it's complete and correct.
>
> It combines a recent patch, "Compute u-area offsets of FP registers
> correctly" with a change I committed to the ppc64-linux branch a while
> back, and forgot to post. The patch I did post:
>
> http://sources.redhat.com/ml/gdb-patches/2003-06/msg00250.html
>
> 2003-06-10 Jim Blandy <jimb@redhat.com>
>
> * ppc-linux-nat.c (ppc_register_u_addr): Correctly compute u-area
> register offsets for both the 32- and 64-bit interfaces.
Okay.
Kevin
prev parent reply other threads:[~2003-06-10 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 16:24 Jim Blandy
2003-06-10 16:32 ` 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=1030610163241.ZM21700@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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