From: Jason R Thorpe <thorpej@wasabisystems.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFA] Move i387 register supply/fill to i387-tdep.c
Date: Thu, 09 May 2002 17:23:00 -0000 [thread overview]
Message-ID: <20020509172324.S3435@dr-evil.shagadelic.org> (raw)
In-Reply-To: <20020510001205.GA15259@nevyn.them.org>; from drow@mvista.com on Thu, May 09, 2002 at 08:12:05PM -0400
On Thu, May 09, 2002 at 08:12:05PM -0400, Daniel Jacobowitz wrote:
> Thanks! This is the biggest chunk of i386 cross core debugging. The
> other nasty one is ARM's evil registers...
I have changes for some of the ARM stuff, too, but I need to clean up
some stuff and then discuss it with Richard.
Note, that I think there might be byte-order snafus in the i387
supply/fill goo, but it'd be nice to move it first, and then fix
the bugs in it :-)
--
-- Jason R. Thorpe <thorpej@wasabisystems.com>
next prev parent reply other threads:[~2002-05-10 0:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 16:45 Jason R Thorpe
2002-05-09 17:12 ` Daniel Jacobowitz
2002-05-09 17:23 ` Jason R Thorpe [this message]
2002-05-09 18:28 ` Daniel Jacobowitz
2002-05-10 3:54 ` Mark Kettenis
2002-05-10 8:10 ` Jason R Thorpe
2002-05-10 0:26 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2002-04-11 16:05 Jason R Thorpe
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=20020509172324.S3435@dr-evil.shagadelic.org \
--to=thorpej@wasabisystems.com \
--cc=gdb-patches@sources.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