qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Lyon <christophe.lyon@st.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] rsqrte_f32: No need to copy sign bit.
Date: Mon, 10 Oct 2011 13:26:36 +0200	[thread overview]
Message-ID: <4E92D66C.1060903@st.com> (raw)
In-Reply-To: <CAFEAcA_h8N8tudY6cxedYP3qXKF-7fyrdxk0EAnxHhnccwgBMg@mail.gmail.com>

On 09.10.2011 00:57, Peter Maydell wrote:
> On 3 October 2011 15:28, Christophe Lyon<christophe.lyon@st.com>  wrote:
>> Indeed, the result is known to be always positive.
>> -    val = ((val64>>  63)&  0x80000000)
>> -        | ((result_exp&  0xff)<<  23)
>> +    val = ((result_exp&  0xff)<<  23)
>>          | ((val64>>  29)&  0x7fffff);
>>      return make_float32(val);
> So we weren't generating incorrect results, we were just doing
> slightly more work than we really needed, right? I'm curious
> what prompted this patch :-)
>
Exactly. And no way to expose a bug :-(

I was reading 2 revisions of the ARM ARM, and noticed erratas in the descriptions of FPRecipEstimate and FPRSqrtEstimate.

Sign propagation has been removed in the former, and not in the later, so I re-read both functions carefully as well as qemu's implementation and came to this conclusion :-)

I have contacted ARM support and suggested them to fix both function accordingly :-)

Christophe.

  reply	other threads:[~2011-10-10 11:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-03 14:28 [Qemu-devel] [PATCH] rsqrte_f32: No need to copy sign bit Christophe Lyon
2011-10-08 22:57 ` Peter Maydell
2011-10-10 11:26   ` Christophe Lyon [this message]
2011-10-10 12:26     ` 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=4E92D66C.1060903@st.com \
    --to=christophe.lyon@st.com \
    --cc=peter.maydell@linaro.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 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).