public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/103707] Stray "Array operands are incommensurate"
Date: Sun, 26 Jun 2022 21:21:26 +0000 [thread overview]
Message-ID: <bug-103707-4-dEWWydq9PI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103707-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103707
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-06-26
CC| |anlauf at gcc dot gnu.org
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #6 from anlauf at gcc dot gnu.org ---
(In reply to Thomas Koenig from comment #5)
> Thanks for the quick reduction, Gerhard.
>
> This originally came from something like
>
> program p
> real, parameter :: fmin(1) = 0.
> real, parameter :: fmax(1) = 1.
> real :: x(1)
> where (fmin <= 0)
> x = fmin + (fmax-fmin)
> elsewhere
> x = (fmax/fmin)**2
> end where
> print *,x
> end
>
> so there is no division by zero at runtime.
Some data points from other compiler that reject the code:
NAG prints
NAG Fortran Compiler Release 7.0(Yurakucho) Build 7009
Error: pr103707.f90, line 8: Floating-point divide by zero
Cray versions 10 thru 14 print:
x = (fmax/fmin)**2
^
ftn-1184 crayftn: WARNING P, File = pr103707.f90, Line = 8, Column = 16
Evaluation of this constant expression produced a NaN or other abnormal
value.
^
ftn-1184 crayftn: WARNING P, File = pr103707.f90, Line = 8, Column = 22
Evaluation of this constant expression produced a NaN or other abnormal
value.
Cray Fortran : Version 14.0.0
(20220420160222_c98838affc7b58fed2a72f164d77c35e1bc8772f)
Intel and Nvidia are silent.
While gfortran's error message is misleading, what is our plan?
Avoid simplification in the frontend?
next prev parent reply other threads:[~2022-06-26 21:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 10:28 [Bug fortran/103707] New: " tkoenig at gcc dot gnu.org
2021-12-14 10:30 ` [Bug fortran/103707] " tkoenig at gcc dot gnu.org
2021-12-14 16:07 ` anlauf at gcc dot gnu.org
2021-12-14 18:16 ` gscfq@t-online.de
2021-12-14 18:27 ` gscfq@t-online.de
2021-12-15 7:58 ` tkoenig at gcc dot gnu.org
2022-06-26 21:21 ` anlauf at gcc dot gnu.org [this message]
2024-03-06 16:57 ` cvs-commit at gcc dot gnu.org
2024-03-06 21:33 ` anlauf at gcc dot gnu.org
2024-04-02 17:07 ` cvs-commit at gcc dot gnu.org
2024-04-02 17:33 ` anlauf at gcc dot gnu.org
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=bug-103707-4-dEWWydq9PI@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).