public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/106785] ICE in fail, at selftest.cc:47 since r13-2266-g8bb1df032cc080
Date: Wed, 31 Aug 2022 12:41:22 +0000	[thread overview]
Message-ID: <bug-106785-4-tjr7LQ6M8r@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106785-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106785

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
If !MODE_HAS_NANS, then NANs can't appear ever, that is the VAX case.
Some floating point formats simply have no representation for those.
If MODE_HAS_NANS && !HONOR_NANS, it is user promising NaNs won't appear but the
floating point format supports them.  Code where NaN would appear is UB, we can
do anything we want, just shouldn't break code where the NaN wouldn't appear at
runtime.  Say
if (cond)
  x = __builtin_nan ("");
else
  x = 1.24;
we can assume that x will never be NaN with -ffinite-math-only.

  parent reply	other threads:[~2022-08-31 12:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31 11:01 [Bug rtl-optimization/106785] New: " marxin at gcc dot gnu.org
2022-08-31 11:18 ` [Bug rtl-optimization/106785] " aldyh at gcc dot gnu.org
2022-08-31 11:30 ` aldyh at gcc dot gnu.org
2022-08-31 11:33 ` aldyh at gcc dot gnu.org
2022-08-31 12:28 ` aldyh at gcc dot gnu.org
2022-08-31 12:41 ` jakub at gcc dot gnu.org [this message]
2022-08-31 13:12 ` aldyh at gcc dot gnu.org
2022-08-31 13:21 ` [Bug tree-optimization/106785] " aldyh at gcc dot gnu.org
2022-08-31 15:11 ` jakub at gcc dot gnu.org
2022-09-01  7:09 ` cvs-commit at gcc dot gnu.org
2022-09-01  7:12 ` aldyh at gcc dot gnu.org

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=bug-106785-4-tjr7LQ6M8r@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).