From: Alexander Graf <agraf@suse.de>
To: Tristan Gingold <gingold@adacore.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] powerpc: use float64 for frsqrte
Date: Tue, 03 Jun 2014 12:02:40 +0200 [thread overview]
Message-ID: <538D9D40.2080105@suse.de> (raw)
In-Reply-To: <1401786860-32216-1-git-send-email-gingold@adacore.com>
On 06/03/2014 11:14 AM, Tristan Gingold wrote:
> Remove the code that reduce the result to float32 as the frsqrte
> instruction is defined to return a double-precision estimate of
> the reciprocal square root.
>
> Although reducing the fractional part is harmless (as the estimation
> must have at least 12 bits of precision according to the old PEM),
> reducing the exponent range is not correct.
>
> Signed-off-by: Tristan Gingold <gingold@adacore.com>
I couldn't find a reference to doubles in ISA 2.07. Is frsqrte supposed
to return doubles on all cores? Or is this implementation specific?
Also, is frsqrte the only instruction affected?
Alex
> ---
> target-ppc/fpu_helper.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/target-ppc/fpu_helper.c b/target-ppc/fpu_helper.c
> index cd8f015..da93d12 100644
> --- a/target-ppc/fpu_helper.c
> +++ b/target-ppc/fpu_helper.c
> @@ -977,7 +977,6 @@ uint64_t helper_fres(CPUPPCState *env, uint64_t arg)
> uint64_t helper_frsqrte(CPUPPCState *env, uint64_t arg)
> {
> CPU_DoubleU farg;
> - float32 f32;
>
> farg.ll = arg;
>
> @@ -991,8 +990,6 @@ uint64_t helper_frsqrte(CPUPPCState *env, uint64_t arg)
> }
> farg.d = float64_sqrt(farg.d, &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;
> }
next prev parent reply other threads:[~2014-06-03 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 9:14 [Qemu-devel] [PATCH] powerpc: use float64 for frsqrte Tristan Gingold
2014-06-03 10:02 ` Alexander Graf [this message]
2014-06-03 13:43 ` Tristan Gingold
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=538D9D40.2080105@suse.de \
--to=agraf@suse.de \
--cc=gingold@adacore.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).