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/104382] Finalization of parent components not compliant with standard
Date: Mon, 07 Feb 2022 15:54:52 +0000 [thread overview]
Message-ID: <bug-104382-4-10ct0KMKgV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104382-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104382
--- Comment #3 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to anlauf from comment #2)
> crayftn 11 & 12 output:
>
> destructor4(complicated) 2*2.
> destructor5 (simple2) 5
> destructor5 (simple2) 6
> destructor2(simple) 2*1
> destructor4(complicated) 4., 5.
> destructor5 (simple2) -1
> destructor5 (simple2) -2
> destructor2(simple) 3, 4
> final_count after assignment = 8
> destructor4(complicated) 4., 5.
> destructor5 (simple2) -1
> destructor5 (simple2) -2
> destructor2(simple) 3, 4
> final_count after deallocation = 12
That seems to make a majority vote for the present gfortran behaviour then.
Thanks
Paul
next prev parent reply other threads:[~2022-02-07 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 12:49 [Bug fortran/104382] New: " pault at gcc dot gnu.org
2022-02-07 11:51 ` [Bug fortran/104382] " pault at gcc dot gnu.org
2022-02-07 15:49 ` anlauf at gcc dot gnu.org
2022-02-07 15:54 ` pault at gcc dot gnu.org [this message]
2022-08-10 7:40 ` tkoenig at gcc dot gnu.org
2022-08-11 6:21 ` paul.richard.thomas at gmail dot com
2022-11-28 15:28 ` pault at gcc dot gnu.org
2023-03-18 17:31 ` 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-104382-4-10ct0KMKgV@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).