From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: Nathan Froyd <froydnj@codesourcery.com>
Subject: [Qemu-devel] [PATCH 0/2] ARM: Implement correct NaN propagation rules
Date: Thu, 16 Dec 2010 11:51:16 +0000 [thread overview]
Message-ID: <1292500278-26215-1-git-send-email-peter.maydell@linaro.org> (raw)
IEEE754 doesn't specify precisely what NaN should be returned as the
result of an operation on two input NaNs. The existing softfloat code
hardwires x87 propagation rules. This patchset abstracts out the code
in the various propagateFloat*NaN() functions which picks a NaN to
return, so that it can be easily replaced on a per-target basis.
It also implements the correct version of this routine for ARM.
I've tested this by the usual random instruction set method. The
first patch makes no change to NaN handling (ie it is purely a
refactoring of the code); the second brings ARM into line with the
hardware implementation.
Maintainers of other targets should consider implementing a suitable
version of the pickNaN() function. I know the SPARC architecture
manual documents NaN rules, and they're not the x87 ones, for instance.
Peter Maydell (2):
softfloat: abstract out target-specific NaN propagation rules
ARM: Implement correct NaN propagation rules
fpu/softfloat-specialize.h | 183 +++++++++++++++++++++++++++++--------------
1 files changed, 123 insertions(+), 60 deletions(-)
next reply other threads:[~2010-12-16 11:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 11:51 Peter Maydell [this message]
2010-12-16 11:51 ` [Qemu-devel] [PATCH 1/2] softfloat: abstract out target-specific NaN propagation rules Peter Maydell
2011-01-02 13:23 ` Aurelien Jarno
2011-01-02 14:04 ` Peter Maydell
2011-01-02 15:05 ` Aurelien Jarno
2011-01-02 15:35 ` Peter Maydell
2011-01-02 23:00 ` Aurelien Jarno
2010-12-16 11:51 ` [Qemu-devel] [PATCH 2/2] ARM: Implement correct " Peter Maydell
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=1292500278-26215-1-git-send-email-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=froydnj@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).