From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH][MIPS] FPU support for MIPS
Date: Thu, 27 Apr 2006 00:17:08 +0200 [thread overview]
Message-ID: <444FF164.2060104@bellard.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0604261622190.30332@mag.sysgo.com>
A few remarks:
1) Why do you use 3 temporaries ? Maybe two suffice in most cases.
2) do_cmp_d() should be completely decoded at translation time.
3) I suspect the macro FPR() does too many things at runtime which gives
an important performance loss. CP0St_FR should be known at translation time.
You should use CONFIG_SOFTFLOAT to validate your code. The ARM target
does it, so it works (see the configure script).
Fabrice.
Marius Groeger wrote:
> Hi All,
>
> a new version of my FPU patch, now actually doing some math. Known
> issues include, but may not be limited to:
>
> - only support .d format, that is IEEE 64bit
> - no proper float exception handling. If someone gets CONFIG_SOFTFLOAT
> to compile, this should be quite easy to improve. Most of
> the infrastructure required is in place.
>
> Feedback welcome!
>
> Cheers,
> Marius
next prev parent reply other threads:[~2006-04-26 22:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 14:26 [Qemu-devel] [PATCH][MIPS] FPU support for MIPS Marius Groeger
2006-04-26 22:17 ` Fabrice Bellard [this message]
2006-04-27 10:22 ` Marius Groeger
2006-05-02 12:06 ` [Qemu-devel] [PATCH][MIPS] Alexander Voropay
2006-05-02 16:14 ` Dirk Behme
-- strict thread matches above, loose matches on Subject: below --
2006-05-02 14:01 [Qemu-devel] [PATCH][MIPS] FPU support for MIPS Marius Groeger
2006-05-02 14:20 ` Marius Groeger
[not found] ` <20060502143520.GB9551@lebarbe.net>
2006-05-03 8:19 ` Marius Groeger
2006-06-08 13:48 Marius Groeger
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=444FF164.2060104@bellard.org \
--to=fabrice@bellard.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.