public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/siddhesh/gai-cleanup2] math: Add more input to atanh accuracy tests Date: Tue, 1 Mar 2022 02:39:25 +0000 (GMT) [thread overview] Message-ID: <20220301023925.D52FD3858418@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=db34e88b86af8eafa59e26aaa2e7abc608d95fb9 commit db34e88b86af8eafa59e26aaa2e7abc608d95fb9 Author: Sunil K Pandey <skpgkp2@gmail.com> Date: Tue Feb 15 12:51:46 2022 -0800 math: Add more input to atanh accuracy tests This patch adds following input to atanh accuracy test. 0x1.f80094p-8 Tested on x86-64 and i686 platforms. Other platforms may have to regenerate ulps file. Reviewed-by: Paul Zimmermann <Paul.Zimmermann@inria.fr> Diff: --- math/auto-libm-test-in | 3 +++ math/auto-libm-test-out-atanh | 25 +++++++++++++++++++++++++ 2 files changed, 28 insertions(+) diff --git a/math/auto-libm-test-in b/math/auto-libm-test-in index 9080afe4fb..30fbada31f 100644 --- a/math/auto-libm-test-in +++ b/math/auto-libm-test-in @@ -617,6 +617,9 @@ atanh -0x3.98eaf4p-4 atanh 0x2.c1085p-4 atanh 0x1p-500 atanh 0x1p-5000 +# the next value generates larger error bounds in libmvec/avx512 on x86_64 +# (binary32) +atanh 0x1.f80094p-8 # the next value generates larger error bounds on x86_64 (binary128) atanh 0x2.c02a24f3472c7840afbd8cfb68bap-4 atanh min diff --git a/math/auto-libm-test-out-atanh b/math/auto-libm-test-out-atanh index 378ef6e8cf..a5243264be 100644 --- a/math/auto-libm-test-out-atanh +++ b/math/auto-libm-test-out-atanh @@ -3112,6 +3112,31 @@ atanh 0x1p-5000 = atanh tonearest binary128 0x1p-5000 : 0x1p-5000 : inexact-ok = atanh towardzero binary128 0x1p-5000 : 0x1p-5000 : inexact-ok = atanh upward binary128 0x1p-5000 : 0x1.0000000000000000000000000001p-5000 : inexact-ok +atanh 0x1.f80094p-8 += atanh downward binary32 0x1.f80094p-8 : 0x1.f8031ep-8 : inexact-ok += atanh tonearest binary32 0x1.f80094p-8 : 0x1.f8032p-8 : inexact-ok += atanh towardzero binary32 0x1.f80094p-8 : 0x1.f8031ep-8 : inexact-ok += atanh upward binary32 0x1.f80094p-8 : 0x1.f8032p-8 : inexact-ok += atanh downward binary64 0x1.f80094p-8 : 0x1.f8031f3228153p-8 : inexact-ok += atanh tonearest binary64 0x1.f80094p-8 : 0x1.f8031f3228154p-8 : inexact-ok += atanh towardzero binary64 0x1.f80094p-8 : 0x1.f8031f3228153p-8 : inexact-ok += atanh upward binary64 0x1.f80094p-8 : 0x1.f8031f3228154p-8 : inexact-ok += atanh downward intel96 0x1.f80094p-8 : 0x1.f8031f3228153f0ep-8 : inexact-ok += atanh tonearest intel96 0x1.f80094p-8 : 0x1.f8031f3228153f0ep-8 : inexact-ok += atanh towardzero intel96 0x1.f80094p-8 : 0x1.f8031f3228153f0ep-8 : inexact-ok += atanh upward intel96 0x1.f80094p-8 : 0x1.f8031f3228153f1p-8 : inexact-ok += atanh downward m68k96 0x1.f80094p-8 : 0x1.f8031f3228153f0ep-8 : inexact-ok += atanh tonearest m68k96 0x1.f80094p-8 : 0x1.f8031f3228153f0ep-8 : inexact-ok += atanh towardzero m68k96 0x1.f80094p-8 : 0x1.f8031f3228153f0ep-8 : inexact-ok += atanh upward m68k96 0x1.f80094p-8 : 0x1.f8031f3228153f1p-8 : inexact-ok += atanh downward binary128 0x1.f80094p-8 : 0x1.f8031f3228153f0e56e4db72d2afp-8 : inexact-ok += atanh tonearest binary128 0x1.f80094p-8 : 0x1.f8031f3228153f0e56e4db72d2bp-8 : inexact-ok += atanh towardzero binary128 0x1.f80094p-8 : 0x1.f8031f3228153f0e56e4db72d2afp-8 : inexact-ok += atanh upward binary128 0x1.f80094p-8 : 0x1.f8031f3228153f0e56e4db72d2bp-8 : inexact-ok += atanh downward ibm128 0x1.f80094p-8 : 0x1.f8031f3228153f0e56e4db72d28p-8 : inexact-ok += atanh tonearest ibm128 0x1.f80094p-8 : 0x1.f8031f3228153f0e56e4db72d28p-8 : inexact-ok += atanh towardzero ibm128 0x1.f80094p-8 : 0x1.f8031f3228153f0e56e4db72d28p-8 : inexact-ok += atanh upward ibm128 0x1.f80094p-8 : 0x1.f8031f3228153f0e56e4db72d3p-8 : inexact-ok atanh 0x2.c02a24f3472c7840afbd8cfb68bap-4 = atanh downward binary32 0x2.c02a28p-4 : 0x2.c73a3cp-4 : inexact-ok = atanh tonearest binary32 0x2.c02a28p-4 : 0x2.c73a3cp-4 : inexact-ok
reply other threads:[~2022-03-01 2:39 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220301023925.D52FD3858418@sourceware.org \ --to=siddhesh@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).