From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Add support for floating point endpoints to frange.
Date: Wed, 31 Aug 2022 09:24:01 -0600 [thread overview]
Message-ID: <b2a29ac7-1f12-ce70-40fa-38e6d59ba135@gmail.com> (raw)
In-Reply-To: <CAGm3qMXyJxfVeW2xSR6JBNDY45_QVCZkmNhmqizjRE3T2H=+iQ@mail.gmail.com>
On 8/29/2022 8:30 AM, Aldy Hernandez via Gcc-patches wrote:
> On Mon, Aug 29, 2022 at 4:27 PM Jakub Jelinek <jakub@redhat.com> wrote:
>> On Mon, Aug 29, 2022 at 04:20:16PM +0200, Aldy Hernandez wrote:
>>> Sure, I can add the HONOR_NANS, but can we even "see" a NAN in the IL
>>> for -ffinite-math-only?
>> Sure, you can, e.g. __builtin_nan{,s}{,f,l} etc. would do it.
>> It would be UB to use it at runtime in -ffinite-math-only code though.
>> Another question is, when making a range VARYING, do you set the NAN
>> property or not when !HONOR_NANS && MODE_HAS_NANS?
> A range of VARYING sets the NAN property to unknown
> (fp_prop::VARYING). If you prefer we can set the property to
> fp_prop::NO for !HONOR_NANS && MODE_HAS_NANS.
If the format doesn't have NaNs or the user explicitly disables them,
then the state should be NO, otherwise YES.
Jeff
next prev parent reply other threads:[~2022-08-31 15:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 11:42 Aldy Hernandez
2022-08-26 15:55 ` Aldy Hernandez
2022-08-26 17:40 ` Andrew Pinski
2022-08-26 18:11 ` Aldy Hernandez
2022-08-26 18:11 ` Aldy Hernandez
2022-08-26 19:16 ` Aldy Hernandez
2022-08-26 19:44 ` Andrew Pinski
2022-08-29 13:45 ` Aldy Hernandez
2022-08-29 13:54 ` Jakub Jelinek
2022-08-29 14:07 ` Toon Moene
2022-08-29 14:15 ` Aldy Hernandez
2022-08-29 14:30 ` Toon Moene
2022-08-29 14:36 ` Aldy Hernandez
2022-08-29 14:42 ` Toon Moene
2022-08-30 9:27 ` Aldy Hernandez
2022-08-31 15:22 ` Jeff Law
2022-08-31 15:19 ` Jeff Law
2022-08-29 14:08 ` Aldy Hernandez
2022-08-29 14:17 ` Jakub Jelinek
2022-08-29 14:20 ` Aldy Hernandez
2022-08-29 14:27 ` Jakub Jelinek
2022-08-29 14:30 ` Aldy Hernandez
2022-08-31 15:24 ` Jeff Law [this message]
2022-08-30 22:32 ` Joseph Myers
2022-08-31 15:16 ` Jeff Law
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=b2a29ac7-1f12-ce70-40fa-38e6d59ba135@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.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).