From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: Joseph Myers <josmyers@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: Ping Re: Implement C23 log2p1
Date: Mon, 29 Apr 2024 15:51:11 +0200 [thread overview]
Message-ID: <p9u0y18wgtv4.fsf@coriandre.loria.fr> (raw)
In-Reply-To: <7468e028-70b-e9d1-1985-70fef8ab950@redhat.com> (message from Joseph Myers on Mon, 29 Apr 2024 13:34:08 +0000 (UTC))
Dear Joseph,
I have already given my opinion on this patch (after sending several hours
to exercise it):
https://sourceware.org/pipermail/libc-alpha/2024-April/156007.html
I now let other people comment.
Paul Zimmermann
> Date: Mon, 29 Apr 2024 13:34:08 +0000 (UTC)
> From: Joseph Myers <josmyers@redhat.com>
>
> I'd like to ping this patch
> <https://sourceware.org/pipermail/libc-alpha/2024-April/155960.html>, and,
> in particular:
>
> (a) the actual content of the patch, which no-one has commented on
> (instead preferring to suggest other things to add to it);
>
> (b) the questions of what goes in such patches, where I argue that we
> should not expect libm-test-ulps updates for more than one architecture,
> or additional test inputs based on searches for worst-case inputs, to be
> included in such a patch: that it should be sufficient to include
> libm-test-ulps updates for a single architecture, and tests that seem
> appropriate based on the mathematical properties of the function being
> tested, and further additions there can reasonably be made in followup
> patches. (Note that even if we moved to a single libm-test-ulps shared
> between architectures and listing expected ulps based on floating-point
> format rather than type, it still wouldn't be possible to update all ulps
> on a single system: no architecture supports both ldbl-96 and
> ldbl-128ibm.)
>
> --
> Joseph S. Myers
> josmyers@redhat.com
>
next prev parent reply other threads:[~2024-04-29 13:51 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
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 [this message]
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=p9u0y18wgtv4.fsf@coriandre.loria.fr \
--to=paul.zimmermann@inria.fr \
--cc=josmyers@redhat.com \
--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).