From: Joseph Myers <joseph@codesourcery.com>
To: Paul Zimmermann <Paul.Zimmermann@inria.fr>
Cc: Paul E Murphy <murphyp@linux.ibm.com>, <libc-alpha@sourceware.org>
Subject: Re: faster expf128
Date: Wed, 24 Jun 2020 17:39:10 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2006241736480.28946@digraph.polyomino.org.uk> (raw)
In-Reply-To: <mw8sgddlup.fsf@tomate.loria.fr>
On Wed, 24 Jun 2020, Paul Zimmermann wrote:
> I forgot to say my code is intended mainly for machines that do not provide
> hardware float128 support. However I did compare with the glibc
> expf128 on gcc135.fsffrance.org (ppc64le GNU/Linux) and below are the
> results. You can reproduce them with the code from [1]. We see that
> my implementation is about 27% faster, but slightly less accurate
> (999585 instead of 999999 correct rounding over 1000000). One caveat
> though: I did not find how to efficiently set the inexact flag, thus
> it is not set in my code.
There is no expectation that most libm functions (other than those such as
fma and sqrt that are fully defined by the corresponding IEEE operations)
set inexact correctly. (It is necessary to set other exceptions
correctly, and the glibc testsuite verifies that; for expf128, that's
invalid (for signaling NaNs), overflow and underflow.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-06-24 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 11:02 Paul Zimmermann
2020-06-22 13:59 ` Paul E Murphy
2020-06-22 21:18 ` Joseph Myers
2020-06-24 6:22 ` Paul Zimmermann
2020-06-24 17:39 ` Joseph Myers [this message]
2020-06-26 10:09 ` Szabolcs Nagy
2020-06-29 22:39 ` Joseph Myers
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.21.2006241736480.28946@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Paul.Zimmermann@inria.fr \
--cc=libc-alpha@sourceware.org \
--cc=murphyp@linux.ibm.com \
/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).