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/111674] New: [13/14 regression] Failure to finalize an allocatable subobject of a non-finalizable type Date: Tue, 03 Oct 2023 10:06:46 +0000 [thread overview] Message-ID: <bug-111674-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111674 Bug ID: 111674 Summary: [13/14 regression] Failure to finalize an allocatable subobject of a non-finalizable type Product: gcc Version: 13.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: pault at gcc dot gnu.org Target Milestone: --- Created attachment 56035 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56035&action=edit Testcase demonstrating the bug Introduced by r13-6747-gd7caf313525a46f200d7f5db1ba893f853774aee See the attached testcase, which was developed to check F2018 compliance in the Chivers/Sleightholme compliance tables. gfortran correctly determines from 7.5.6.1 that y is not finalizable. However, following the first paragraph in 7.5.6.3, the component y%aa should be finalized before deallocation in the second assignment. 12-branch used to do this but 13-branch and mainline currently do not. Note, that 12-branch does not finalize x in its second assignment, as it should. Fortunately the fix is trivial and will be posted in the first comment. Paul
next reply other threads:[~2023-10-03 10:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-03 10:06 pault at gcc dot gnu.org [this message] 2023-10-03 10:11 ` [Bug fortran/111674] " pault at gcc dot gnu.org 2023-10-03 18:50 ` anlauf at gcc dot gnu.org 2023-10-04 7:26 ` cvs-commit at gcc dot gnu.org 2023-10-04 8:22 ` cvs-commit at gcc dot gnu.org 2023-10-04 8:24 ` 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-111674-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).