public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig 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: Wed, 10 Aug 2022 07:40:31 +0000 [thread overview] Message-ID: <bug-104382-4-eg1MOwd3Cr@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 Thomas Koenig <tkoenig at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tkoenig at gcc dot gnu.org --- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> --- To add some variety to the tests, nagfor gives destructor4(complicated) 2.0000000 2.0000000 destructor5 (simple2) 5 destructor5 (simple2) 6 destructor2(simple) 1 1 final_count after assignment = 4 destructor4(complicated) 4.0000000 5.0000000 destructor5 (simple2) -1 destructor5 (simple2) -2 destructor2(simple) 3 4 final_count after deallocation = 8
next prev parent reply other threads:[~2022-08-10 7:40 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 2022-08-10 7:40 ` tkoenig at gcc dot gnu.org [this message] 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-eg1MOwd3Cr@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: linkBe 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).