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:05:00 -0000 [thread overview] Message-ID: <bug-47637-4-jCduv85YeZ@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 janus at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #6 from janus at gcc dot gnu.org 2011-02-09 16:01:04 UTC --- Fixed with r169978. Thanks for the report, Rich! Note that further memory leaks are to expected for cases where the dynamic type is different from the declared type (and has additional allocatable components), cf. PR 46321.
prev parent reply other threads:[~2011-02-09 16:01 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 2011-02-09 16:05 ` janus at gcc dot gnu.org [this message]
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-jCduv85YeZ@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: linkBe 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).