From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org
Cc: Florian Weimer <fweimer@redhat.com>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [PATCH 1/5] x86 long double: Support pseudo numbers in fpclassifyl
Date: Wed, 23 Dec 2020 07:13:11 +0530 [thread overview]
Message-ID: <2c580aff-11cf-68d5-ebd3-62c22d1d8adf@sourceware.org> (raw)
In-Reply-To: <4c72ae2e-c7fd-f3c4-f840-9fefa169b1e0@linaro.org>
On 12/23/20 12:13 AM, Adhemerval Zanella via Libc-alpha wrote:
>
>
> On 15/12/2020 11:13, Siddhesh Poyarekar via Libc-alpha wrote:
>> ---
>> sysdeps/i386/fpu/s_fpclassifyl.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/sysdeps/i386/fpu/s_fpclassifyl.c b/sysdeps/i386/fpu/s_fpclassifyl.c
>> index 501312f51e..aeaec7279c 100644
>> --- a/sysdeps/i386/fpu/s_fpclassifyl.c
>> +++ b/sysdeps/i386/fpu/s_fpclassifyl.c
>> @@ -34,6 +34,10 @@ __fpclassifyl (long double x)
>> retval = FP_ZERO;
>> else if (ex == 0 && (hx & 0x80000000) == 0)
>> retval = FP_SUBNORMAL;
>> + /* Pseudo-normals, i.e. pseudo-zero, pseudo-infinity and unnormals. They
>
> Intel manual adds a hyphen for un-normals.
>
Fixed.
>> + behave like NaNs, so categorize them as such. */
>> + else if ((hx & 0x80000000) == 0)
>> + retval = FP_NAN;
>
> Ok.
>
>> else if (ex == 0x7fff)
>> retval = ((hx & 0x7fffffff) | lx) != 0 ? FP_NAN : FP_INFINITE;
>>
>>
>
> Maybe move the implementation to sysdep/x86/fpu since it is used for
> both x86_64 and i386? It avoid the implicit cross abi include the
> and make the implementation selection more clear.
>
OK.
Thanks,
Siddhesh
next prev parent reply other threads:[~2020-12-23 1:43 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 [this message]
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
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=2c580aff-11cf-68d5-ebd3-62c22d1d8adf@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--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).