public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/94361] [8/9/10/11 Regression] Memory leak in nested types with final
Date: Sat, 23 May 2020 19:13:28 +0000 [thread overview]
Message-ID: <bug-94361-4-rv91hNb3SY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94361-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94361
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
--- Comment #5 from anlauf at gcc dot gnu.org ---
Reverting the commit
commit b81f7b83631be7dedcdcf44eed6dd575ada3ac23
Author: Thomas Koenig <tkoenig@gcc.gnu.org>
Date: Sat Apr 6 22:10:28 2019 +0000
re PR fortran/87352 (Large stack usage with new gfortran)
2019-04-06 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/87352
* gfortran.h (gfc_component): Add finalized field.
* class.c (finalize_component): If the component is already
finalized, return early. Set component->finalized on exit.
2019-04-06 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/87352
* gfortran.dg/finalize_28.f90: Adjust count of __builtin_free.
* gfortran.dg/finalize_33.f90: Likewise.
* gfortran.dg/finalize_34.f90: New test.
From-SVN: r270184
fixes the memory leak.
CCing Thomas.
next prev parent reply other threads:[~2020-05-23 19:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 16:46 [Bug fortran/94361] New: " antony at cosmologist dot info
2020-05-18 19:11 ` [Bug fortran/94361] " anlauf at gcc dot gnu.org
2020-05-18 19:12 ` anlauf at gcc dot gnu.org
2020-05-18 21:30 ` antony at cosmologist dot info
2020-05-19 9:15 ` antony at cosmologist dot info
2020-05-21 10:39 ` [Bug fortran/94361] [8/9/10/11 Regression] " anlauf at gcc dot gnu.org
2020-05-23 19:13 ` anlauf at gcc dot gnu.org [this message]
2020-05-24 12:26 ` tkoenig at gcc dot gnu.org
2020-05-31 10:00 ` cvs-commit at gcc dot gnu.org
2020-06-01 18:16 ` cvs-commit at gcc dot gnu.org
2020-06-01 18:33 ` cvs-commit at gcc dot gnu.org
2020-06-01 18:49 ` cvs-commit at gcc dot gnu.org
2020-06-01 18:52 ` tkoenig 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-94361-4-rv91hNb3SY@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).