From: FX <fxcoudert@gmail.com>
To: Harald Anlauf <anlauf@gmx.de>
Cc: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org, hjl@sc.intel.com
Subject: Re: [PATCH] Fortran: make IEEE_CLASS recognize signaling NaNs
Date: Tue, 11 Jan 2022 23:32:55 +0100 [thread overview]
Message-ID: <2AC9FA3C-2E70-4A5B-B612-FDF0E00BA845@gmail.com> (raw)
In-Reply-To: <b789fe91-cb8e-7a0a-9e6b-2bf7e4332aa4@gmx.de>
Hi HJ,
> I looked at gcc-testresults and find e.g.
>
> https://gcc.gnu.org/pipermail/gcc-testresults/2022-January/747938.html
> https://gcc.gnu.org/pipermail/gcc-testresults/2022-January/747935.html
>
> which is x86 (64 and 32 bit) by H.J.; plus some more.
> Maybe H.J. can explain what is different from your platform?
Could you kindly look up what the log says for these failures on your boxes:
FAIL: gfortran.dg/ieee/signaling_1.f90 -O0 (test for excess errors)
UNRESOLVED: gfortran.dg/ieee/signaling_1.f90 -O0 compilation failed to produce executable
Somehow they did not seem to show up on my test machine. I’m launching a fresh bootstrap, but it will take a while.
FX
next prev parent reply other threads:[~2022-01-11 22:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 10:50 FX
2022-01-09 10:52 ` FX
2022-01-09 19:34 ` Mikael Morin
2022-01-10 12:04 ` FX
2022-01-11 22:01 ` Harald Anlauf
2022-01-11 22:01 ` Harald Anlauf
2022-01-11 22:04 ` FX
2022-01-11 22:11 ` Harald Anlauf
2022-01-11 22:11 ` Harald Anlauf
2022-01-11 22:32 ` FX [this message]
2022-01-12 10:23 ` FX
2022-01-12 10:34 ` Jakub Jelinek
2022-01-12 11:03 ` FX
2022-01-12 11:06 ` Jakub Jelinek
2022-01-12 11:55 ` 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=2AC9FA3C-2E70-4A5B-B612-FDF0E00BA845@gmail.com \
--to=fxcoudert@gmail.com \
--cc=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl@sc.intel.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).