From: Jeff Law <jeffreyalaw@gmail.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
Jakub Jelinek <jakub@redhat.com>
Cc: Aldy Hernandez <aldyh@redhat.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
GCC patches <gcc-patches@gcc.gnu.org>,
Andrew MacLeod <amacleod@redhat.com>
Subject: Re: [PATCH] Implement range-op entry for sin/cos.
Date: Mon, 24 Apr 2023 10:33:38 -0600 [thread overview]
Message-ID: <b0d82260-4520-00d9-7e91-4cc6fb3271fd@gmail.com> (raw)
In-Reply-To: <477bddf7-63e8-cfa8-a1db-330ca7bfb896@gotplt.org>
On 4/24/23 10:05, Siddhesh Poyarekar wrote:
> On 2023-04-24 12:03, Jakub Jelinek wrote:
>> On Thu, Apr 20, 2023 at 01:57:55PM -0400, Siddhesh Poyarekar wrote:
>>>> Similarly for other functions which have other ranges, perhaps not
>>>> with so
>>>> nice round numbers. Say asin has [-pi/2, pi/2] range, those numbers
>>>> aren't
>>>> exactly representable, but is it any worse to round those values to
>>>> -inf or
>>>> +inf or worse give something 1-5 ulps further from that interval
>>>> comparing
>>>> to other 1-5ulps errors?
>>
>> I've extended my hack^^^test to include sqrt and this time it seems
>> that the boundary in that case holds even for non-standard rounding modes
>> for glibc:
>
> IIRC the standard _requires_ sqrt to be correctly rounded.
Correct. I spent an inordinate amount of time dealing with this in the
past ;-)
jeff
next prev parent reply other threads:[~2023-04-24 16:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 13:12 Aldy Hernandez
2023-04-20 12:59 ` Jakub Jelinek
2023-04-20 13:17 ` Siddhesh Poyarekar
2023-04-20 14:02 ` Jakub Jelinek
2023-04-20 14:20 ` Jakub Jelinek
2023-04-20 15:22 ` Siddhesh Poyarekar
2023-04-20 15:52 ` Jakub Jelinek
2023-04-20 17:57 ` Siddhesh Poyarekar
2023-04-21 1:14 ` Siddhesh Poyarekar
2023-04-21 6:52 ` Jakub Jelinek
2023-04-21 11:20 ` Siddhesh Poyarekar
2023-04-25 8:59 ` Aldy Hernandez
2023-04-24 16:03 ` Jakub Jelinek
2023-04-24 16:05 ` Siddhesh Poyarekar
2023-04-24 16:09 ` Jakub Jelinek
2023-04-24 16:33 ` Jeff Law [this message]
2023-04-21 16:40 ` Jakub Jelinek
2023-04-21 20:43 ` Mikael Morin
2023-04-21 20:45 ` Jakub Jelinek
2023-04-25 9:10 ` Aldy Hernandez
2023-04-25 9:08 ` Aldy Hernandez
2023-04-27 11:13 ` [PATCH] v2: " Jakub Jelinek
2023-04-27 11:46 ` Aldy Hernandez
2023-04-27 11:53 ` Jakub Jelinek
2023-04-27 12:03 ` Aldy Hernandez
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=b0d82260-4520-00d9-7e91-4cc6fb3271fd@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=aldyh@redhat.com \
--cc=amacleod@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=siddhesh@gotplt.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).