public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Waterman <andrew@sifive.com>
To: "wilson at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: [Bug target/102211] [12 regression] ICE introduced by r12-3277
Date: Thu, 9 Sep 2021 16:49:57 -0700	[thread overview]
Message-ID: <CA++6G0BETezWy7Lo7PgKC_XerOw_bc6TatCNWvkW2Wdgd817Zg@mail.gmail.com> (raw)
In-Reply-To: <bug-102211-4-yyZBmYYfBq@http.gcc.gnu.org/bugzilla/>

On Tue, Sep 7, 2021 at 10:55 PM wilson at gcc dot gnu.org via Gcc-bugs
<gcc-bugs@gcc.gnu.org> wrote:
>
> The hardware may trap if
> you access a 32-bit value which is not properly NaN-boxed.

I don't think the following affects the resolution of the ticket, but
just for the record, trapping is _not_ an option the ISA permits.  The
only legal outcome from using an improperly NaN-boxed value as an
argument to an instruction that requires NaN-boxed inputs is that the
canonical NaN is substituted in its place.


  reply	other threads:[~2021-09-09 23:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06  2:53 [Bug target/102211] New: " crazylht at gmail dot com
2021-09-06  4:38 ` [Bug target/102211] " crazylht at gmail dot com
2021-09-06  4:50 ` crazylht at gmail dot com
2021-09-07  8:00 ` [Bug target/102211] [12 regression] " schwab@linux-m68k.org
2021-09-07  8:06 ` pinskia at gcc dot gnu.org
2021-09-08  5:55 ` wilson at gcc dot gnu.org
2021-09-09 23:49   ` Andrew Waterman [this message]
2021-09-08  5:55 ` wilson at gcc dot gnu.org
2021-09-09  5:31 ` wilson at gcc dot gnu.org
2021-09-09 23:30 ` segher at gcc dot gnu.org
2021-09-09 23:50 ` andrew at sifive dot com
2021-09-10 21:55 ` cvs-commit at gcc dot gnu.org
2021-09-13 17:35 ` wilson at gcc dot gnu.org
2021-09-13 17:43 ` wilson at gcc dot gnu.org
2022-01-17 13:33 ` rguenth at gcc dot gnu.org
2022-01-17 13:34 ` rguenth 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=CA++6G0BETezWy7Lo7PgKC_XerOw_bc6TatCNWvkW2Wdgd817Zg@mail.gmail.com \
    --to=andrew@sifive.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-bugzilla@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).