From: Peter Maydell <peter.maydell@linaro.org>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH 3/3] target-ppc: fix sNaN propagation
Date: Mon, 10 Jan 2011 18:14:18 -0600 [thread overview]
Message-ID: <AANLkTikFFPXX_m6XpHkn3MSdo2nBX=mN4AfcnFY2=Cfs@mail.gmail.com> (raw)
In-Reply-To: <1293979183-27108-4-git-send-email-aurelien@aurel32.net>
On 2 January 2011 08:39, Aurelien Jarno <aurelien@aurel32.net> wrote:
> The current FPU code returns 0.0 if one of the operand is a
> signaling NaN and the VXSNAN exception is disabled.
>
> fload_invalid_op_excp() doesn't return a qNaN in case of a VXSNAN
> exception as the operand should be propagated instead of a new
> qNaN to be generated. Fix that by calling fload_invalid_op_excp()
> only for the exception generation (if enabled), and use the softfloat
> code to correctly compute the result.
>
> Cc: Alexander Graf <agraf@suse.de>
> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
> @@ -1410,10 +1418,10 @@ uint64_t helper_frsp (uint64_t arg)
> if (unlikely(float64_is_signaling_nan(farg.d))) {
> /* sNaN square root */
> farg.ll = fload_invalid_op_excp(POWERPC_EXCP_FP_VXSNAN);
> - } else {
> - f32 = float64_to_float32(farg.d, &env->fp_status);
> - farg.d = float32_to_float64(f32, &env->fp_status);
> }
> + f32 = float64_to_float32(farg.d, &env->fp_status);
> + farg.d = float32_to_float64(f32, &env->fp_status);
> +
> return farg.ll;
> }
Most of these changes are to ignoring the result from
fload_invalid_op_excp(POWERPC_EXCP_FP_VXSNAN),
but this one leaves it assigning a value to farg.ll -- is there
any reason for that? (It looks like the assignment gets
immediately overwritten by the assignment to farg.d later.)
> @@ -1460,11 +1468,11 @@ uint64_t helper_fres (uint64_t arg)
> if (unlikely(float64_is_signaling_nan(farg.d))) {
> /* sNaN reciprocal */
> farg.ll = fload_invalid_op_excp(POWERPC_EXCP_FP_VXSNAN);
> - } else {
> - farg.d = float64_div(float64_one, farg.d, &env->fp_status);
> - f32 = float64_to_float32(farg.d, &env->fp_status);
> - farg.d = float32_to_float64(f32, &env->fp_status);
> }
> + farg.d = float64_div(float64_one, farg.d, &env->fp_status);
> + f32 = float64_to_float32(farg.d, &env->fp_status);
> + farg.d = float32_to_float64(f32, &env->fp_status);
> +
> return farg.ll;
> }
>
Ditto for this hunk.
Looks plausible to me other than that.
-- PMM
next prev parent reply other threads:[~2011-01-11 0:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-02 14:39 [Qemu-devel] [PATCH 0/3] target-ppc: improve FPU emulation Aurelien Jarno
2011-01-02 14:39 ` [Qemu-devel] [PATCH 1/3] target-ppc: remove PRECISE_EMULATION define Aurelien Jarno
2011-01-05 17:02 ` [Qemu-devel] " Alexander Graf
2011-01-02 14:39 ` [Qemu-devel] [PATCH 2/3] target-ppc: fix default qNaN Aurelien Jarno
2011-01-05 17:09 ` [Qemu-devel] " Alexander Graf
2011-01-06 15:03 ` Aurelien Jarno
2011-01-02 14:39 ` [Qemu-devel] [PATCH 3/3] target-ppc: fix sNaN propagation Aurelien Jarno
2011-01-05 17:20 ` [Qemu-devel] " Alexander Graf
2011-01-10 19:26 ` Aurelien Jarno
2011-01-11 0:14 ` Peter Maydell [this message]
2011-01-11 6:23 ` [Qemu-devel] " Aurelien Jarno
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='AANLkTikFFPXX_m6XpHkn3MSdo2nBX=mN4AfcnFY2=Cfs@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=agraf@suse.de \
--cc=aurelien@aurel32.net \
--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).