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/104272] finalizer gets called during allocate
Date: Wed, 05 Apr 2023 06:29:41 +0000	[thread overview]
Message-ID: <bug-104272-4-Jew1QYjnEV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104272-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Paul Thomas <pault at gcc dot gnu.org> ---
Created attachment 54811
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54811&action=edit
Fix for this PR

I was sufficiently intrigued by this bug that I decided that I would look into
it right away. After all, it is the first time that such an old finalization
problem was producing too many calls to the final subroutine.

I'll be posting to the list after checking the deja-gnuified testcase.

Paul

  parent reply	other threads:[~2023-04-05  6:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 18:40 [Bug fortran/104272] New: " kai.germaschewski at gmail dot com
2023-04-02 20:12 ` [Bug fortran/104272] " anlauf at gcc dot gnu.org
2023-04-03 16:17 ` pault at gcc dot gnu.org
2023-04-03 16:28 ` pault at gcc dot gnu.org
2023-04-05  6:29 ` pault at gcc dot gnu.org [this message]
2023-04-05 13:26 ` kai.germaschewski at gmail dot com
2023-04-14 10:15 ` cvs-commit at gcc dot gnu.org
2023-04-14 13:41 ` 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-104272-4-Jew1QYjnEV@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).