public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: FX <fxcoudert@gmail.com>
Cc: fortran@gcc.gnu.org
Subject: Re: New signaling NaN causes 12 testsuite failures
Date: Tue, 25 Jan 2022 12:20:29 -0800	[thread overview]
Message-ID: <20220125202029.GD69322@troutmask.apl.washington.edu> (raw)
In-Reply-To: <B41D2A33-2345-4169-842B-FD92F8E1C61B@gmail.com>

On Tue, Jan 25, 2022 at 09:04:05PM +0100, FX wrote:
> This is x86_64-linux, with the same source:
> 
> $ gcc-10 v.c -fsignaling-nans && ./a.out
> Quiet NaN
> nan 7fc00000
> nan 7ff8000000000000
> nan 564e29277fffc000000000000000
> Signaling NaN
> nan 7fa00000
> nan 7ff4000000000000
> nan 564e29277fffa000000000000000
> 

So the 7fffc and 7fffa signatures are equivalent to
what I see on FreeBSD (never seen the 564e2927 string
before).  Maybe an off-by-one bit in issignaling_fallback.h?

-- 
Steve

  reply	other threads:[~2022-01-25 20:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25  0:44 Steve Kargl
2022-01-25  2:48 ` Steve Kargl
2022-01-25  8:05   ` FX
2022-01-25 17:42     ` Steve Kargl
2022-01-25 19:59     ` Steve Kargl
2022-01-25 20:04       ` FX
2022-01-25 20:20         ` Steve Kargl [this message]
2022-01-25  8:09 ` FX
2022-01-25 16:52   ` Steve Kargl
2022-01-25 19:35   ` Steve Kargl
2022-01-25 19:52     ` FX
2022-01-25 20:12       ` Steve Kargl
2022-01-25 20:45       ` Steve Kargl
2022-01-25 20:56         ` FX
2022-01-25 21:05           ` Steve Kargl
2022-01-25 23:11             ` FX
2022-01-26 10:47           ` Tobias Burnus
2022-01-26 16:02             ` Steve Kargl
2022-01-26 16:19               ` FX

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=20220125202029.GD69322@troutmask.apl.washington.edu \
    --to=sgk@troutmask.apl.washington.edu \
    --cc=fortran@gcc.gnu.org \
    --cc=fxcoudert@gmail.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).