public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/63473] Memory leak with ALLOCATABLE, INTENT(OUT) dummy arguments.
Date: Tue, 16 Dec 2014 15:34:00 -0000	[thread overview]
Message-ID: <bug-63473-4-2LXCa7XFfU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63473-4@http.gcc.gnu.org/bugzilla/>

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

janus at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[4.9/5 Regression] Memory   |Memory leak with
                   |leak with ALLOCATABLE,      |ALLOCATABLE, INTENT(OUT)
                   |INTENT(OUT) dummy           |dummy arguments.
                   |arguments.                  |

--- Comment #5 from janus at gcc dot gnu.org ---
-fdump-tree-original shows the following:


            if (array.data != 0B)
              {
                __builtin_free ((void *) array.data);
              }
            array.data = 0B;
            allocate_mytype (&array);


So: Before the call to 'allocate_mytype', the array itself is being
auto-deallocated, but its components are not!


  parent reply	other threads:[~2014-12-16 15:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07 18:06 [Bug fortran/63473] New: " paul.vandelst at noaa dot gov
2014-12-16 14:50 ` [Bug fortran/63473] [4.9/5 Regression] " janus at gcc dot gnu.org
2014-12-16 15:13 ` janus at gcc dot gnu.org
2014-12-16 15:26 ` janus at gcc dot gnu.org
2014-12-16 15:34 ` janus at gcc dot gnu.org [this message]
2015-08-07 17:26 ` [Bug fortran/63473] " mikael 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-63473-4-2LXCa7XFfU@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).