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/93691] Type bound assignment causes too many finalization of derived type when part of other type
Date: Sat, 18 Mar 2023 17:25:36 +0000	[thread overview]
Message-ID: <bug-93691-4-2yGvuUtTyj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93691-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93691

Paul Thomas <pault at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED
                 CC|                            |pault at gcc dot gnu.org

--- Comment #4 from Paul Thomas <pault at gcc dot gnu.org> ---
Hi Florian,

I am closing this as fixed, even though it runs to the third finalization and
then segfaults, because both nagfor and ifort behave in the same way.

The dump of the code shows that Outer2 is finalized before the assignment and
that both Outer1 and Outer2 are finalized on leaving the block scope. Thus,
alll is as it should be.

Default initializing icount to NULL(), guarding for unassociated icount in
deleteIt gets rid of the segfault.

Thanks for the report.

Paul

      parent reply	other threads:[~2023-03-18 17:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-93691-4@http.gcc.gnu.org/bugzilla/>
2020-06-01 19:13 ` tkoenig at gcc dot gnu.org
2020-06-03  6:32 ` mscfd at gmx dot net
2023-03-18  7:56 ` cvs-commit at gcc dot gnu.org
2023-03-18 17:25 ` pault at gcc dot gnu.org [this message]

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-93691-4-2yGvuUtTyj@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).