From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Paul Zimmermann <Paul.Zimmermann@inria.fr>
Cc: libc-alpha@sourceware.org
Subject: Re: [COMMITTED] aarch64: Update ulps
Date: Tue, 21 May 2024 09:20:45 -0300 [thread overview]
Message-ID: <eaa5c226-cb5a-4294-a38c-004edff76ecf@linaro.org> (raw)
In-Reply-To: <p9u0bk4za7qe.fsf@araignee.loria.fr>
Hi Paul,
Not really, I just regenerate the ulps values from the 'make regen-ulps'
rule that uses current tests.
On 21/05/24 05:29, Paul Zimmermann wrote:
> Hi Adhemerval,
>
> did you check if the values from
> https://sourceware.org/pipermail/libc-alpha/2024-April/156007.html
> generate larger errors?
>
> Paul
>
>> From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
>> Date: Mon, 20 May 2024 13:45:49 -0300
>>
>> For the log2p1 implementation.
>> ---
>> sysdeps/aarch64/libm-test-ulps | 20 ++++++++++++++++++++
>> 1 file changed, 20 insertions(+)
>>
>> diff --git a/sysdeps/aarch64/libm-test-ulps b/sysdeps/aarch64/libm-test-ulps
>> index 6d083c4e32..9a7e775c85 100644
>> --- a/sysdeps/aarch64/libm-test-ulps
>> +++ b/sysdeps/aarch64/libm-test-ulps
>> @@ -1371,6 +1371,26 @@ double: 3
>> float: 3
>> ldouble: 1
>>
>> +Function: "log2p1":
>> +double: 1
>> +float: 1
>> +ldouble: 3
>> +
>> +Function: "log2p1_downward":
>> +double: 2
>> +float: 2
>> +ldouble: 3
>> +
>> +Function: "log2p1_towardzero":
>> +double: 2
>> +float: 2
>> +ldouble: 2
>> +
>> +Function: "log2p1_upward":
>> +double: 1
>> +float: 2
>> +ldouble: 2
>> +
>> Function: "log_advsimd":
>> double: 1
>> float: 3
>> --
>> 2.43.0
>>
>>
next prev parent reply other threads:[~2024-05-21 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 16:45 Adhemerval Zanella
2024-05-21 8:29 ` Paul Zimmermann
2024-05-21 12:20 ` Adhemerval Zanella Netto [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-01 12:33 [COMMITTED] aarch64: update ulps Szabolcs Nagy
2020-12-21 16:44 Szabolcs Nagy
2020-08-13 12:16 Szabolcs Nagy
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=eaa5c226-cb5a-4294-a38c-004edff76ecf@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=Paul.Zimmermann@inria.fr \
--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).