From: Fabrice Bellard <fabrice@bellard.org>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Patch ping
Date: Mon, 21 Feb 2005 21:34:28 +0100 [thread overview]
Message-ID: <421A45D4.1090609@bellard.org> (raw)
In-Reply-To: <200502201919.27396.paul@codesourcery.com>
Paul Brook wrote:
> I posted a patch implementing arm vfp emulation over a week ago, and it seems
> to have passed without comment:
>
> http://lists.gnu.org/archive/html/qemu-devel/2005-02/msg00131.html
It seems that you like C macros :-) Can you suppress the operations to
read or write FP registers ? You can add just a few ops to read or write
to a constant offset in the CPU state. It seems that a generic IEEE
library is needed in QEMU now because most CPUs need the same operations...
Fabrice.
next prev parent reply other threads:[~2005-02-21 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 19:19 [Qemu-devel] Patch ping Paul Brook
2005-02-21 20:34 ` Fabrice Bellard [this message]
2005-02-21 23:46 ` [Qemu-devel] Arm VFP Paul Brook
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=421A45D4.1090609@bellard.org \
--to=fabrice@bellard.org \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).