From: Joseph Myers <josmyers@redhat.com>
To: Paul Zimmermann <Paul.Zimmermann@inria.fr>
Cc: libc-alpha@sourceware.org
Subject: Re: Implement C23 log2p1
Date: Wed, 10 Apr 2024 15:00:36 +0000 (UTC) [thread overview]
Message-ID: <5b9b8e-f24-5581-d21b-e0ab4d8e28ca@redhat.com> (raw)
In-Reply-To: <p9u0h6g9z367.fsf@araignee.loria.fr>
On Wed, 10 Apr 2024, Paul Zimmermann wrote:
> Hi Joseph,
>
> I would prefer that you submit a v2 including the inputs yielding larger
> errors that I pointed out in my review.
I think that's out of scope for this patch in the same way that adding
benchmarks, or optimized function implementations for particular formats,
or for that matter updating all the architecture-specific libm-test-ulps
files, is out of scope: the design for this patch, and thus for all the
subsequent patches adding such APIs (TS 18661-4 interfaces adopted in
C23), is to provide the API and ABI in glibc with everything required for
such a new interface (including being sufficiently accurate that errors
are within the bounds accepted in libm-test-ulps files, and having tests
of a representative range of inputs), but going for simplicity of
implementation rather than trying to cover things that can reasonably be
done in subsequent incremental improvements after the API and ABI have
been added.
--
Joseph S. Myers
josmyers@redhat.com
next prev parent reply other threads:[~2024-04-10 15:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 21:19 Joseph Myers
2024-04-10 8:31 ` Paul Zimmermann
2024-04-10 14:34 ` Joseph Myers
2024-04-10 14:46 ` Paul Zimmermann
2024-04-10 15:00 ` Joseph Myers [this message]
2024-04-15 13:41 ` Carlos O'Donell
2024-04-15 13:52 ` Adhemerval Zanella Netto
2024-04-18 13:26 ` Joseph Myers
2024-04-29 13:34 ` Ping " Joseph Myers
2024-04-29 13:51 ` Paul Zimmermann
2024-05-07 21:34 ` Ping^2 " Joseph Myers
2024-05-16 16:47 ` Ping^3 " 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=5b9b8e-f24-5581-d21b-e0ab4d8e28ca@redhat.com \
--to=josmyers@redhat.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).