From: FX <fxcoudert@gmail.com>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: fortran@gcc.gnu.org
Subject: Re: New signaling NaN causes 12 testsuite failures
Date: Tue, 25 Jan 2022 09:05:55 +0100 [thread overview]
Message-ID: <93B4F458-9AD2-44DA-9F21-37B16C4A0CE8@gmail.com> (raw)
In-Reply-To: <20220125024811.GA19308@troutmask.apl.washington.edu>
Hi Steve,
> New signaling NaN causes 12 testsuite failures
Thanks for alerting me.
> Line 42 of signal_1.f90 looks wrong unless the
> line is testing conversion on assignment. Should
> y be x?
Indeed. Fixed: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=c0a4a658097c56fa03d04b8d15c3ea02961d62a4
> Got the following in testsuite/gfortran/gfortran.log
>
> NaN 7FFFA000000000000000
> NaN 7FFFC000000000000000
> NaN 7FFFA000000000000000
>
> and with "stop 300" commented out everything passes. Now to
> chase down hex representations for sNaN and qNaN. Suspect
> ieee_class() is broken.
How does the long double formation look like on x86_64-unknown-freebsd?
That test passes on x86_64 for linux and darwin, so I’m wondering what’s different about freebsd…
Can you tell me whether the C front-end defines __LDBL_IS_IEC_60559__? What is the value of __LDBL_DIG__? __DBL_DIG__? __FLOAT_WORD_ORDER == __BIG_ENDIAN or __LITTLE_ENDIAN?
FX
next prev parent reply other threads:[~2022-01-25 8:05 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 [this message]
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
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=93B4F458-9AD2-44DA-9F21-37B16C4A0CE8@gmail.com \
--to=fxcoudert@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
/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).