From: Joseph Myers <joseph@codesourcery.com>
To: Paul Zimmermann <Paul.Zimmermann@inria.fr>
Cc: <libc-alpha@sourceware.org>, <vincenzo.innocente@cern.ch>
Subject: Re: Accuracy of Mathematical Functions
Date: Fri, 11 Feb 2022 18:23:58 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2202111813400.245895@digraph.polyomino.org.uk> (raw)
In-Reply-To: <mw7da195j8.fsf@tomate.loria.fr>
On Fri, 11 Feb 2022, Paul Zimmermann wrote:
> Hi,
>
> with the release of GNU libc 2.35, we have published a new version of our
> comparison of the accuracy of mathematical libraries:
>
> https://members.loria.fr/PZimmermann/papers/accuracy.pdf
>
> For the GNU libc, with respect to 2.34, we observed an improvement in j0f,
> tgamma, hypot, hypotl and hypotf128.
>
> With respect to the previous update, we compare two new libraries: LLVM libc
> and ROCm.
Thanks for the update. A few remarks on things it might be interesting to
add to the analysis:
1. I don't know if any of those libraries include any of the new functions
C23 adds from TS 18661-4 (beyond exp10), but if they do, it might be worth
adding them to the comparison. (My remarks from
<https://sourceware.org/pipermail/libc-alpha/2022-January/135006.html>
apply regarding adding them to glibc - when I get time I hope to add them,
as with other new C23 features, if no-one else has done them by then.)
2. I don't know if any of those libraries have IEEE binary16 functions (C
_Float16), but again, if any do, they might be worth testing (in that
case, exhaustive testing should be possible for functions of two
arguments, not just functions of a single argument).
3. As previously remarked, FreeBSD libm is another implementation that
might be worth testing (though that would require running the tests on a
FreeBSD system).
4. As previously remarked, it would be interesting to see similar data for
complex functions (real and imaginary parts of the result of a function
with one complex argument being essentially the same as the case of a
function with a real result and two real arguments).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-02-11 18:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 8:22 Paul Zimmermann
2022-02-11 18:23 ` Joseph Myers [this message]
2022-02-12 6:39 ` Paul Zimmermann
2022-02-15 1:52 ` Joseph Myers
-- strict thread matches above, loose matches on Subject: below --
2024-08-06 12:24 Paul Zimmermann
2024-08-06 15:27 ` Joseph Myers
2024-08-07 10:37 ` Paul Zimmermann
2024-08-08 16:35 ` Joseph Myers
2024-08-09 8:16 ` Paul Zimmermann
2024-08-09 12:54 ` Adhemerval Zanella Netto
2024-08-09 15:57 ` Joseph Myers
2024-02-15 14:47 Paul Zimmermann
2023-09-21 7:11 Paul Zimmermann
2023-02-14 8:05 Paul Zimmermann
2022-08-29 10:41 Paul Zimmermann
2021-09-07 14:45 Paul Zimmermann
2021-02-05 10:35 accuracy of mathematical functions 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.2202111813400.245895@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Paul.Zimmermann@inria.fr \
--cc=libc-alpha@sourceware.org \
--cc=vincenzo.innocente@cern.ch \
/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).