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/25095] Disallowed intrinsic in initialization statement
Date: Tue, 22 Aug 2023 19:29:10 +0000 [thread overview]
Message-ID: <bug-25095-4-Z9rvrnh18S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-25095-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25095
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
CC| |anlauf at gcc dot gnu.org
--- Comment #8 from anlauf at gcc dot gnu.org ---
(In reply to Jürgen Reuter from comment #7)
> Indeed, ifort and PGI fortran flag this as an error in the implied DO
> expression. Nagfor flags it just as an extension.
Actually, current nagfor flags it as:
% nagfor pr25095.f90 -f2003
NAG Fortran Compiler Release 7.1(Hanzomon) Build 7101
Extension(F2008): pr25095.f90, line 2: Function reference in DATA-implied-DO
[NAG Fortran Compiler normal termination, 1 warning]
and is silent for -f2008 or -f2018 .
The F2018 (and similarly F2008) text is slightly clearer here:
! C881 (R841) In an array-element or scalar-structure-component that is a
! data-i-do-object, any subscript shall be a constant expression, and any
! primary within that subscript that is a data-i-do-variable shall be a
! DO variable of this data-implied-do or of a containing data-implied-do.
and then
! 10.1.12 Constant expression
!
! (5) a reference to an elemental standard intrinsic function, where each
! argument is a constant expression,
!
! (11) a data-i-do-variable within a data-implied-do,
!
! and Note 1
and among the standard intrinsic procedures:
! 16.9.136 MODULO (A, P)
So this is more likely an ifort and PGI/Nvidia bug on the one hand, and
on the other the question whether we care for a diagnostic for -std=f95 .
next parent reply other threads:[~2023-08-22 19:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-25095-4@http.gcc.gnu.org/bugzilla/>
2023-08-22 19:29 ` anlauf at gcc dot gnu.org [this message]
2023-08-26 17:00 ` anlauf at gcc dot gnu.org
2005-11-26 18:06 [Bug fortran/25095] New: better diagnostic needed jv244 at cam dot ac dot uk
2006-06-04 9:52 ` [Bug fortran/25095] Disallowed intrinsic in initialization statement fxcoudert at gcc dot gnu dot org
2006-06-04 10:43 ` jv244 at cam dot ac dot uk
2007-05-21 19:07 ` dfranke at gcc dot gnu dot org
2007-10-07 19:43 ` tobi at gcc dot gnu dot org
2007-10-07 19:49 ` tobi at gcc dot gnu dot org
2008-01-04 11:08 ` dfranke at gcc dot gnu dot 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-25095-4-Z9rvrnh18S@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).