From: Toon Moene <toon@moene.org>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Add support for floating point endpoints to frange.
Date: Mon, 29 Aug 2022 16:30:09 +0200 [thread overview]
Message-ID: <c8ba1f90-6ba9-e280-4398-aa042fd0c5d7@moene.org> (raw)
In-Reply-To: <CAGm3qMV_PM=1dwUfybfXGFEN3EHsb1hB=9qcGaN8Nerr+CB-cQ@mail.gmail.com>
On 8/29/22 16:15, Aldy Hernandez wrote:
> But even with -ffinite-math-only, is there any benefit to propagating
> a known NAN? For example:
The original intent (in 2002) for the option -ffinite-math-only was for
the optimizers to ignore all the various exceptions to common
optimizations because they might not work correctly when presented with
a NaN or an Inf.
I do not know what the effect for floating point range information would
be - offhand.
But in the *spirit* of this option would be to ignore that the range
[5.0, 5.0] would "also" contain NaN, for instance.
Kind regards,
--
Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
next prev parent reply other threads:[~2022-08-29 14:30 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 [this message]
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
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=c8ba1f90-6ba9-e280-4398-aa042fd0c5d7@moene.org \
--to=toon@moene.org \
--cc=aldyh@redhat.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).