From: Joseph Myers <joseph@codesourcery.com>
To: Paul Zimmermann <Paul.Zimmermann@inria.fr>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCH] add inputs to auto-libm-test-in yielding larger errors
Date: Mon, 30 Nov 2020 22:21:24 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2011302217420.724571@digraph.polyomino.org.uk> (raw)
In-Reply-To: <mw5z5nrv3i.fsf@tomate.loria.fr>
On Mon, 30 Nov 2020, Paul Zimmermann wrote:
> Dear Joseph,
>
> submitted as https://sourceware.org/bugzilla/show_bug.cgi?id=26982, and a
> similar one for tgamma (https://sourceware.org/bugzilla/show_bug.cgi?id=26983).
Thanks. It would be interesting to know if similar cases can be found for
other floating-point formats (inputs with large errors for different
formats could go in the same bugs rather than needing a separate bug for
each format) as that might affect how many implementations need to get
similar fixes. You've done exhaustive searches for float. But have you
looked for such large errors for these functions for ldbl-96 (x86 extended
precision) or ldbl-128 (binary128), for example? (Or for ldbl-128ibm,
with the larger threshold of permitted errors there and the definition of
ulps that treats it like a format with exactly 106 bits of precision.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-11-30 22:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 18:10 Paul Zimmermann
2020-11-25 22:05 ` Joseph Myers
2020-11-26 8:16 ` Paul Zimmermann
2020-11-27 19:13 ` Joseph Myers
2020-11-30 10:34 ` Paul Zimmermann
2020-11-30 22:21 ` Joseph Myers [this message]
2020-12-01 10:29 ` Paul Zimmermann
2020-12-01 22:48 ` Joseph Myers
2020-12-02 6:42 ` Paul Zimmermann
2020-12-21 5:09 ` Siddhesh Poyarekar
2020-12-09 10:05 Paul Zimmermann
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=alpine.DEB.2.22.394.2011302217420.724571@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--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).