From: FX <fxcoudert@gmail.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Weird behaviour (bug?) of __builtin_nans()
Date: Fri, 31 Dec 2021 20:14:02 +0100 [thread overview]
Message-ID: <A3E12C73-5000-4007-9E25-CA251997FBFC@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2112311653250.2293191@digraph.polyomino.org.uk>
Hi Joseph,
> 1. You should use -fsignaling-nans if you want signaling NaNs to work
> correctly.
Thanks, we’ll compile the libgfortran parts that are IEEE-related with that from now on. Sounds like a good idea, anyway.
> 3. There is probably a reasonable case for interpreting such conversions
> (including casts) as copy operations instead, including in the absence of
> -fsignaling-nans; C23 Annex F leaves that implementation-defined, and
> handling such conversions as copy operations is likely to be more
> predictable and more useful.
I agree that while there may be no guarantee, it sounds like a reasonable expectation in the case I posted. I’ve filed a PR: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103883
Thanks,
FX
prev parent reply other threads:[~2021-12-31 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 16:13 FX
2021-12-31 17:05 ` Joseph Myers
2021-12-31 19:14 ` FX [this message]
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=A3E12C73-5000-4007-9E25-CA251997FBFC@gmail.com \
--to=fxcoudert@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
/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).