public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh 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:28:18 +0000	[thread overview]
Message-ID: <bug-106785-4-c3UPzbBZIt@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

Aldy Hernandez <aldyh at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #4 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
For !HONOR_NANS we know x >= 5.0 will not contain a NAN, but what about
explicit NANs in the code, for example the result of __builtin_nan?

Is [NAN, NAN] != [NAN, NAN] like we do for HONOR_NANS?

Are the following selftests applicable for !HONOR_NANS?

  // NAN U NAN = NAN
  // NAN ^ NAN = NAN
  // VARYING ^ NAN = NAN.

It would seem yes, but I'd like to make sure.

  parent reply	other threads:[~2022-08-31 12:28 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 [this message]
2022-08-31 12:41 ` jakub at gcc dot gnu.org
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-c3UPzbBZIt@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).