public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Paul Zimmermann <zimmerma@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] added pair of inputs for hypotf in binary32
Date: Tue, 14 Feb 2023 08:41:38 +0000 (GMT)	[thread overview]
Message-ID: <20230214084138.D3A2F3858D1E@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=cf7ffdd8a5f6da55397e10b3860062944312824c

commit cf7ffdd8a5f6da55397e10b3860062944312824c
Author: Paul Zimmermann <Paul.Zimmermann@inria.fr>
Date:   Sun Feb 12 08:01:18 2023 +0100

    added pair of inputs for hypotf in binary32
    
    This pair yields an error of 1 ulp in binary32, whereas the current
    maximal known error for hypotf on x86_64 is zero:
    
    Checking hypot with glibc-2.37
    hypot 0 -1 -0x1.003222p-20,-0x1.6a2d58p-32 [0.501] 0.500001 0.500000001392678
    libm gives 0x1.003224p-20
    mpfr gives 0x1.003222p-20
    
    See https://sourceware.org/pipermail/libc-alpha/2023-February/145432.html
    and https://sourceware.org/pipermail/libc-alpha/2023-February/145442.html
    Reviewed-by: Carlos O'Donell <carlos@redhat.com>

Diff:
---
 math/auto-libm-test-in | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/math/auto-libm-test-in b/math/auto-libm-test-in
index 393d9fcfaa..c400cafb4b 100644
--- a/math/auto-libm-test-in
+++ b/math/auto-libm-test-in
@@ -5773,6 +5773,8 @@ hypot 0x1p-16384 0x1p-16446
 hypot 0x1p-16383 0x1p-16494
 
 hypot -0x1.fa7deap+0 0x1.a761bab383ac8p+0
+# the following inputs yield an error of 1 ulp on x86_64 in binary32
+hypot -0x1.003222p-20 -0x1.6a2d58p-32
 
 j0 -1.0
 j0 0.0

                 reply	other threads:[~2023-02-14  8:41 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=20230214084138.D3A2F3858D1E@sourceware.org \
    --to=zimmerma@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: 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).