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/47637] [OOP] Memory leak involving INTENT(OUT) CLASS argument w/ allocatable components
Date: Wed, 09 Feb 2011 16:01:00 -0000	[thread overview]
Message-ID: <bug-47637-4-ySeVCpCRZI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47637-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47637

--- Comment #5 from janus at gcc dot gnu.org 2011-02-09 15:58:11 UTC ---
Author: janus
Date: Wed Feb  9 15:58:05 2011
New Revision: 169978

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=169978
Log:
2011-02-09  Janus Weil  <janus@gcc.gnu.org>

    PR fortran/47637
    * trans-decl.c (init_intent_out_dt): Handle CLASS arguments.


2011-02-09  Janus Weil  <janus@gcc.gnu.org>

    PR fortran/47637
    * gfortran.dg/auto_dealloc_2.f90: New.

Added:
    trunk/gcc/testsuite/gfortran.dg/auto_dealloc_2.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/trans-decl.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2011-02-09 15:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 22:15 [Bug fortran/47637] New: Memory leak involving derived types " townsend at astro dot wisc.edu
2011-02-08 20:16 ` [Bug fortran/47637] [OOP] Memory leak involving INTENT(OUT) CLASS argument " janus at gcc dot gnu.org
2011-02-08 22:51 ` janus at gcc dot gnu.org
2011-02-09 10:01 ` janus at gcc dot gnu.org
2011-02-09 14:10 ` burnus at gcc dot gnu.org
2011-02-09 16:01 ` janus at gcc dot gnu.org [this message]
2011-02-09 16:05 ` janus 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-47637-4-ySeVCpCRZI@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).