From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org
Subject: Re: [PATCH 4/5] x86 long double: Consider pseudo numbers as signaling
Date: Wed, 23 Dec 2020 07:20:19 +0530 [thread overview]
Message-ID: <b7a93c74-0453-e991-1ce3-28db4b0c7edf@gotplt.org> (raw)
In-Reply-To: <ff2a0804-fc53-0181-5000-403899914bbc@linaro.org>
On 12/23/20 1:43 AM, Adhemerval Zanella via Libc-alpha wrote:
>
>
> On 15/12/2020 11:13, Siddhesh Poyarekar via Libc-alpha wrote:
>> Implement a separate x86 version of issignalingl that returns true for
>> pseudo-normal numbers.
>>
>> Also drop comment from the generic version of s_issignalingl since it
>> is no longer true or relevant.
>> ---
>> sysdeps/ieee754/ldbl-96/s_issignalingl.c | 2 --
>> sysdeps/x86/fpu/s_issignalingl.c | 39 ++++++++++++++++++++++++
>> 2 files changed, 39 insertions(+), 2 deletions(-)
>> create mode 100644 sysdeps/x86/fpu/s_issignalingl.c
>>
>> diff --git a/sysdeps/ieee754/ldbl-96/s_issignalingl.c b/sysdeps/ieee754/ldbl-96/s_issignalingl.c
>> index ec542ad468..2aa0ffae0e 100644
>> --- a/sysdeps/ieee754/ldbl-96/s_issignalingl.c
>> +++ b/sysdeps/ieee754/ldbl-96/s_issignalingl.c
>> @@ -34,8 +34,6 @@ __issignalingl (long double x)
>> hxi ^= 0x40000000;
>> /* If lxi != 0, then set any suitable bit of the significand in hxi. */
>> hxi |= (lxi | -lxi) >> 31;
>> - /* We do not recognize a pseudo NaN as sNaN; they're invalid on 80387 and
>> - later. */
>> /* We have to compare for greater (instead of greater or equal), because x's
>> significand being all-zero designates infinity not NaN. */
>> return ((exi & 0x7fff) == 0x7fff) && (hxi > 0xc0000000);
>> diff --git a/sysdeps/x86/fpu/s_issignalingl.c b/sysdeps/x86/fpu/s_issignalingl.c
>
> We have multiple internal defines that try to use the common implementation
> instead of pushing for arch-specific ones (for instance nan-high-order-bit.h,
> fix-int-fp-convert-zero.h, fix-fp-int-convert-overflow.h, etc). Maybe it
> would be simpler to just add a new header (nan-handle-pseudo-number.h or
> something related) and adapt the generic implementation.
OK I'll try to do that.
Thanks,
Siddhesh
next prev parent reply other threads:[~2020-12-23 1:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 14:13 [PATCH 0/5] x86 pseudo-normal numbers Siddhesh Poyarekar
2020-12-15 14:13 ` [PATCH 1/5] x86 long double: Support pseudo numbers in fpclassifyl Siddhesh Poyarekar
2020-12-22 18:43 ` Adhemerval Zanella
2020-12-23 1:43 ` Siddhesh Poyarekar
2020-12-15 14:13 ` [PATCH 2/5] x86 long double: Support pseudo numbers in isnanl Siddhesh Poyarekar
2020-12-22 19:04 ` Adhemerval Zanella
2020-12-23 1:49 ` Siddhesh Poyarekar
2020-12-23 8:34 ` Siddhesh Poyarekar
2020-12-15 14:13 ` [PATCH 3/5] Partially revert 681900d29683722b1cb0a8e565a0585846ec5a61 Siddhesh Poyarekar
2020-12-15 14:36 ` Florian Weimer
2020-12-15 15:01 ` Siddhesh Poyarekar
2020-12-15 14:13 ` [PATCH 4/5] x86 long double: Consider pseudo numbers as signaling Siddhesh Poyarekar
2020-12-22 20:13 ` Adhemerval Zanella
2020-12-23 1:50 ` Siddhesh Poyarekar [this message]
2020-12-15 14:13 ` [PATCH 5/5] x86 long double: Add tests for pseudo normal numbers Siddhesh Poyarekar
2020-12-22 21:48 ` Adhemerval Zanella
2020-12-23 1:58 ` Siddhesh Poyarekar
2020-12-23 10:20 ` Siddhesh Poyarekar
2020-12-23 17:44 ` Adhemerval Zanella
2020-12-24 0:48 ` Siddhesh Poyarekar
2020-12-15 18:26 ` [PATCH 0/5] x86 pseudo-normal numbers Joseph Myers
2020-12-15 18:29 ` Siddhesh Poyarekar
2020-12-18 4:03 ` [PING][PATCH " Siddhesh Poyarekar
2020-12-22 7:46 ` [PING*2][PATCH " Siddhesh Poyarekar
2020-12-22 11:11 ` Adhemerval Zanella
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=b7a93c74-0453-e991-1ce3-28db4b0c7edf@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).