From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Paul Zimmermann <Paul.Zimmermann@inria.fr>
Cc: libc-alpha@sourceware.org
Subject: Re: accuracy of j0f
Date: Tue, 03 Aug 2021 18:45:09 +0200 [thread overview]
Message-ID: <8735rqh3ze.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <mw4kc64mk7.fsf@tomate.loria.fr> (Paul Zimmermann's message of "Tue, 03 Aug 2021 16:42:16 +0200")
* Paul Zimmermann:
> 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?
I'd prefer a new bug for this, so that we can reference it in the commit
and backport to the 2.34 release branch.
Thanks,
Florian
next prev parent reply other threads:[~2021-08-03 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 14:42 accuracy of j0f Paul Zimmermann
2021-08-03 16:45 ` Florian Weimer via Libc-alpha [this message]
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=8735rqh3ze.fsf@oldenburg.str.redhat.com \
--to=libc-alpha@sourceware.org \
--cc=Paul.Zimmermann@inria.fr \
--cc=fweimer@redhat.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).