From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: libc-alpha@sourceware.org
Subject: accuracy of j0f
Date: Tue, 03 Aug 2021 16:42:16 +0200 [thread overview]
Message-ID: <mw4kc64mk7.fsf@tomate.loria.fr> (raw)
Hi,
I noticed while testing glibc-2.34 that one of the last minute changes I did
to my patch for j0f was completely wrong. The consequence is that the maximal
error for j0f is still about 900000 ulps and not 9 ulps as claimed. The good
news is that it is not worse than the previous situation from 2.33.
The fix is very easy. Should I reopen bug #14469 or simply send the fix
to the list?
Other Bessel functions (j1, y0, y1) are not affected.
Paul
next reply other threads:[~2021-08-03 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 14:42 Paul Zimmermann [this message]
2021-08-03 16:45 ` accuracy of j0f Florian Weimer via Libc-alpha
2021-08-04 7:49 ` 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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mw4kc64mk7.fsf@tomate.loria.fr \
--to=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).