qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH v1] softfloat: add float128_is_{normal, denormal}
Date: Wed, 6 Feb 2019 09:49:19 +0100	[thread overview]
Message-ID: <f6797f15-759a-3a1a-a7bd-9f22a6dc34f1@redhat.com> (raw)
In-Reply-To: <69586972-35c7-4941-4b65-6b49fed66532@linaro.org>

On 06.02.19 04:08, Richard Henderson wrote:
> On 2/5/19 4:22 PM, David Hildenbrand wrote:
>> +static inline bool float128_is_normal(float128 a)
>> +{
>> +    return ((a.high + (1ULL << 47)) & -1ULL >> 1) >= 1ULL << 48;
> 
> I believe this is off by one: 1 << 48 and >= 1 << 49.
> 
> The exponent is at [62:48].  The trick is adding 1, letting Inf+NaN overflow
> into the sign, masking out the sign, and checking that the result >= 2 to
> eliminate Inf+NaN (0) and Zero+Denormal (1).

Right, the exponent must not be 0 or all 1's. so after adding 1, it must
be >=2.

Yesterday it all made sense on my sheet of paper :) Let's verify against
float64

float64 has an exponent of 11:

return ((float64_val(a) + (1ULL << 52)) & -1ULL >> 1) >= 1ULL << 53;

float128 has an exponent of 15, the difference is 4. So 52 -> 48, 53 -> 49.

So you're right.

> 
> I think this is clearer as
> 
>   (((a.high >> 48) + 1) & 0x7fff) >= 2.>
> It might be worth applying this to the other formats for clarity...
> 

Yes, this makes it much clearer, will send a patch for the others as
well, thanks!

> 
> r~
> 


-- 

Thanks,

David / dhildenb

      reply	other threads:[~2019-02-06  9:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 16:22 [Qemu-devel] [PATCH v1] softfloat: add float128_is_{normal, denormal} David Hildenbrand
2019-02-06  3:08 ` Richard Henderson
2019-02-06  8:49   ` David Hildenbrand [this message]

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=f6797f15-759a-3a1a-a7bd-9f22a6dc34f1@redhat.com \
    --to=david@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=aurelien@aurel32.net \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).