From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfa] Cross corefile support for ARM
Date: Wed, 12 Jul 2006 20:46:00 -0000 [thread overview]
Message-ID: <20060712204633.GT24622@nevyn.them.org> (raw)
In-Reply-To: <1151069710.29989.17.camel@pc960.cambridge.arm.com>
On Fri, Jun 23, 2006 at 02:35:10PM +0100, Richard Earnshaw wrote:
> I wanted to review this against the problem that there are at least 3
> different FPA-flavoured interfaces in linux: NWFPE, NWFPE with extended
> precision and genuine FPA11, and that each of these has a slightly
> different format for the values returned via the ptrace interface (yes,
> this is really a bug in ARM linux, but it ain't going to get fixed
> now...). However, I'm now happy your patch doesn't make things either
> better or worse in this regard.
Yes, that was my goal. In fact preserving the current FPA behavior
took most of the time (and is probably the least useful bit of the
patch).
Thanks, I've committed it.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-07-12 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 15:24 Daniel Jacobowitz
2006-06-23 12:42 ` Daniel Jacobowitz
2006-06-23 13:36 ` Richard Earnshaw
2006-07-12 20:46 ` Daniel Jacobowitz [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=20060712204633.GT24622@nevyn.them.org \
--to=drow@false.org \
--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