public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drikosev at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/64290] [F03] No finalization at deallocation of LHS Date: Tue, 12 Jan 2021 13:03:38 +0000 [thread overview] Message-ID: <bug-64290-4-fM2XZV7DRK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64290-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64290 --- Comment #4 from Ev Drikos <drikosev at gmail dot com> --- Hello, There are some open PRs related to elemental finalisers. Having seen how you reallocate arrays, I'd the impression that the functionality for polymorphic entities would had a similar design. As one may also need ie to reset at least the '_len' field, ie class(*) x; x='a'; Which in turn may not cause regressions to "finalize_25.f90" and I see that this test counts some finalisation calls. Of course I don't doubt that finalization may be partially implemented as you say. Admittedly the interpretation of 10.2.1.3 & 7.5.6.3 seems to be a herculean task. To my understanding, an outcome of the discussion in c.l.f is that the reallocation takes place if the LHS & RHS have different runtime types, at least this seems to be a criterion for no rank polymorphic entities. Hope this helps, Ev. Drikos
next prev parent reply other threads:[~2021-01-12 13:03 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-12 16:26 [Bug fortran/64290] New: Destructor not called " baradi09 at gmail dot com 2014-12-15 11:46 ` [Bug fortran/64290] [F03] No finalization " janus at gcc dot gnu.org 2021-01-11 8:17 ` pault at gcc dot gnu.org 2021-01-12 12:04 ` pault at gcc dot gnu.org 2021-01-12 13:03 ` drikosev at gmail dot com [this message] 2021-01-18 8:32 ` drikosev at gmail dot com 2021-05-04 12:31 ` rguenth at gcc dot gnu.org 2022-12-16 9:28 ` drikosev at gmail dot com 2023-03-18 7:56 ` cvs-commit at gcc dot gnu.org 2023-03-18 12:23 ` 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-64290-4-fM2XZV7DRK@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).