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/106576] Finalization of temporaries from functions not occuring
Date: Tue, 06 Dec 2022 06:12:21 +0000 [thread overview]
Message-ID: <bug-106576-4-RHM8Xc7EcJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106576-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106576
--- Comment #7 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to Thomas Koenig from comment #6)
>
> > I hope that you are well and that the lack of time is for a good cause?
>
> Hi Paul,
>
> yes, I'm well, and the lack of time is indeed for a good cause :-)
>
> > I have just returned to my finalizer patch. With it applied, your testcase
> > produces the same output as NAG.
>
> That's great!
>
> > I will attach the present version of the patch to this PR.
>
> Is there a chance that we will see this patch in gcc13? Even if it
> does not fix every last bug in finalizers in gfortran, it would still
> be a very large improvement compared to the current condition.
Hi Thomas,
It's good to hear from you. I hope to submit the patches before Christmas. I am
working on some final wrinkles and testcases. I am still intensely busy on the
daytime job, which is something of a blocker.
Regards
Paul
next prev parent reply other threads:[~2022-12-06 6:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 7:45 [Bug fortran/106576] New: " tkoenig at gcc dot gnu.org
2022-08-10 16:50 ` [Bug fortran/106576] " tkoenig at gcc dot gnu.org
2022-08-13 16:09 ` tkoenig at gcc dot gnu.org
2022-11-12 15:55 ` tkoenig at gcc dot gnu.org
2022-11-28 15:11 ` pault at gcc dot gnu.org
2022-11-28 15:12 ` pault at gcc dot gnu.org
2022-12-04 17:27 ` tkoenig at gcc dot gnu.org
2022-12-06 6:12 ` pault at gcc dot gnu.org [this message]
2023-03-18 7:56 ` cvs-commit at gcc dot gnu.org
2023-03-18 17:34 ` 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-106576-4-RHM8Xc7EcJ@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).