public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "baradi09 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/64290] New: Destructor not called at deallocation of LHS Date: Fri, 12 Dec 2014 16:26:00 -0000 [thread overview] Message-ID: <bug-64290-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64290 Bug ID: 64290 Summary: Destructor not called at deallocation of LHS Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: baradi09 at gmail dot com Created attachment 34268 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34268&action=edit Self contained source demonstrating During an assingment with an allocatable type on both, the LHS and the RHS, the destructor of the LHS-type is not called. IMHO, this is erroneous behaviour as the LHS gets (hopfully) deallocated on the assignment.
next reply other threads:[~2014-12-12 16:26 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-12 16:26 baradi09 at gmail dot com [this message] 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 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@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).