public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/97122] Spurious FINAL ... must be in the specification part of a MODULE
Date: Mon, 08 May 2023 06:09:36 +0000 [thread overview]
Message-ID: <bug-97122-4-CF4dK7ptC8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97122-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97122
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #10 from Paul Thomas <pault at gcc dot gnu.org> ---
Nagfor responds to the test case with "Error: pr97122.f90, line 14: Type T has
final subroutines but is not defined in the specification part of a module"
F2018:
"C787(R753) A final-subroutine-name shall be the name of a module procedure
with exactly one dummy argument."
Since, of necessity, the argument is declared to be of the derived type with
the final binding, the gfortran and nagfor errors are correct IMHO. ifort
compiles it without complaint.
I have marked this as "waiting" pending a contrary interpretation.
Cheers
Paul
(In reply to kargl from comment #9)
> (In reply to kargl from comment #7)
> > (In reply to kargl from comment #5)
> > > (In reply to Paul Thomas from comment #3)
> > > >
> > > > I have marked this as "waiting" pending a contrary interpretation.
> > > >
> > > > Cheers
> > > >
> > >
> > > Paul,
> > >
> > > I asked on the J3 mailing list about the code.
> > >
> > > https://mailman.j3-fortran.org/pipermail/j3/2023-May/014193.html
> >
> > I haven't had a response from a current member of J3. Bob Corbett,
> > a former member, believes the code is valid Fortran. Jeff Hammond
> > notes that Cray Fortran compiled the code. So, we have Cray, Intel
> > compile the code. NAG and gfortran reject it. I'm not sure if there
> > are any other compilers with submodule support.
>
> Malcolm Cohen from NAG has responded in the J3 list
> that it's a bug in nagfor, and the code in the bug
> report is conforming Fortran.
OK That's good enough for me :-) Changing to new.
Paul
next prev parent reply other threads:[~2023-05-08 6:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 0:21 [Bug fortran/97122] New: " ian_harvey at bigpond dot com
2020-09-20 3:26 ` [Bug fortran/97122] " kargl at gcc dot gnu.org
2023-05-04 6:13 ` pault at gcc dot gnu.org
2023-05-04 8:07 ` pault at gcc dot gnu.org
2023-05-04 17:45 ` kargl at gcc dot gnu.org
2023-05-04 19:01 ` kargl at gcc dot gnu.org
2023-05-04 22:17 ` ian_harvey at bigpond dot com
2023-05-07 15:59 ` kargl at gcc dot gnu.org
2023-05-07 18:41 ` anlauf at gcc dot gnu.org
2023-05-08 1:16 ` kargl at gcc dot gnu.org
2023-05-08 6:09 ` pault at gcc dot gnu.org [this message]
2023-05-23 5:33 ` cvs-commit at gcc dot gnu.org
2023-09-07 19:04 ` anlauf at gcc dot gnu.org
2023-09-09 11:00 ` pault 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-97122-4-CF4dK7ptC8@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).