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/65347] [F03] Final subroutine not called for function result
Date: Fri, 14 Apr 2023 13:59:52 +0000 [thread overview]
Message-ID: <bug-65347-4-Drlz4NmrDl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65347-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65347
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Paul Thomas <pault at gcc dot gnu.org> ---
I am closing this as fixed.
The original testcase output now agrees with nagfor. The testcase of comment #3
produces the same output as nagfor and ifort. ifort finalizes the function call
Ctfin(10) in the original testcase, which is certainly not required by the
F2018 standard and was explicitly deleted in a revision to the F2008 standard.
Finalization of structure and array constructors is all over the place with the
different compilers. I therefore am taking the view that complying with F2018
is the best that can be hoped for.
Sorry this has taken so long to address.
Paul
prev parent reply other threads:[~2023-04-14 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 13:31 [Bug fortran/65347] New: Final subroutine are not called eddyg_61-bugzilla at yahoo dot it
2015-03-20 9:09 ` [Bug fortran/65347] [F03] Final subroutine not called for function result janus at gcc dot gnu.org
2022-04-02 0:47 ` damian at archaeologic dot codes
2023-03-18 15:06 ` pault at gcc dot gnu.org
2023-04-14 13:59 ` pault at gcc dot gnu.org [this message]
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-65347-4-Drlz4NmrDl@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).