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/38319] Memory leaks in allocatable component expressions
Date: Mon, 01 Feb 2021 12:54:54 +0000	[thread overview]
Message-ID: <bug-38319-4-40fCzKtiqa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-38319-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to Tobias Burnus from comment #11)
> Related / same issue:
> https://gcc.gnu.org/pipermail/fortran/2021-January/055654.html

Hi Tobias,

Over the weekend, I had a stab at fixing this recent issue. I can fix this but
at the risk of increasing the problem of leaks in the original examples in this
PR and causing some regressions.

I am going to make the testcase for PR98342 leak free so that the the specific
problems are separated.

Cheers

Paul

  parent reply	other threads:[~2021-02-01 12:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-38319-4@http.gcc.gnu.org/bugzilla/>
2012-02-22 13:34 ` xiaoyuanbo at yeah dot net
2015-01-03 10:19 ` janus at gcc dot gnu.org
2015-01-03 13:33 ` janus at gcc dot gnu.org
2021-02-01  8:29 ` burnus at gcc dot gnu.org
2021-02-01 12:54 ` pault at gcc dot gnu.org [this message]
2008-11-29 21:55 [Bug fortran/38319] New: " pault at gcc dot gnu dot org
2008-11-29 21:55 ` [Bug fortran/38319] " pault at gcc dot gnu dot org
2009-07-30 19:07 ` burnus at gcc dot gnu dot org
2010-02-24 20:31 ` pault at gcc dot gnu dot org
2010-02-25  7:38 ` burnus at gcc dot gnu dot org
2010-02-25 12:51 ` paul dot richard dot thomas at gmail dot com
2010-02-25 13:54 ` burnus at gcc dot gnu dot 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-38319-4-40fCzKtiqa@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).