From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: fortran@gcc.gnu.org, fxcoudert@gmail.com
Subject: Re: New signaling NaN causes 12 testsuite failures
Date: Mon, 24 Jan 2022 18:48:11 -0800 [thread overview]
Message-ID: <20220125024811.GA19308@troutmask.apl.washington.edu> (raw)
In-Reply-To: <20220125004453.GA16729@troutmask.apl.washington.edu>
On Mon, Jan 24, 2022 at 04:44:53PM -0800, Steve Kargl wrote:
> % gmake check-fortran RUNTESTFLAGS="ieee.exp=sign\*"
>
Line 42 of signal_1.f90 looks wrong unless the
line is testing conversion on assignment. Should
y be x?
Instrumented signal_1.f90.
Changed
if (ieee_class(z) /= ieee_signaling_nan) stop 300
to
if (ieee_class(z) /= ieee_signaling_nan) then
print '(G0,1X,Z0)', z, z
z = ieee_value(z, ieee_quiet_nan)
print '(G0,1X,Z0)', z, z
z = ieee_value(z, ieee_signaling_nan)
print '(G0,1X,Z0)', z, z
! stop 300
end if
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.
--
Steve
next prev parent reply other threads:[~2022-01-25 2:48 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 [this message]
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
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=20220125024811.GA19308@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).