qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] Re: [PATCH] target-ppc: use float32_is_any_nan()
Date: Wed, 5 Jan 2011 17:14:04 +0000	[thread overview]
Message-ID: <AANLkTikys9OqKee0ZPfZp1Jh3OqMU88qEmKt6htF8ikv@mail.gmail.com> (raw)
In-Reply-To: <011E3F52-C10D-4087-BDB6-155A4FB5EED3@suse.de>

On 5 January 2011 16:59, Alexander Graf <agraf@suse.de> wrote:
>
> On 02.01.2011, at 13:06, Aurelien Jarno wrote:
>
>> Use the new function float32_is_any_nan() instead of
>> float32_is_quiet_nan() || float32_is_signaling_nan().
>>
>> Cc: Alexander Graf <agraf@suse.de>
>> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
>
> I frankly have very little knowledge of FP stuff. Is any_nan really equal to quiet_nan || signaling_nan or would it cover more cases?

It is exactly equivalent -- all NaNs are either signalling or quiet.

(If you want to check this you don't need to know anything about floating
point, all three functions are just acting on 32 bit values so you could
in theory identify all the bit patterns they return true or false on...)

-- PMM

  reply	other threads:[~2011-01-05 17:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-02 12:06 [Qemu-devel] [PATCH] target-ppc: use float32_is_any_nan() Aurelien Jarno
2011-01-05 16:59 ` [Qemu-devel] " Alexander Graf
2011-01-05 17:14   ` Peter Maydell [this message]
2011-01-05 17:19     ` Alexander Graf
2011-01-05 17:04 ` [Qemu-devel] " Nathan Froyd

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=AANLkTikys9OqKee0ZPfZp1Jh3OqMU88qEmKt6htF8ikv@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).