public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/57762] [4.9 Regression] Memory leak in gfortran.dg/class_array_7.f03 after revision 200084
Date: Tue, 02 Jul 2013 09:43:00 -0000 [thread overview]
Message-ID: <bug-57762-4-Du4u23l8Vi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57762-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57762
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2013-07-02
Ever confirmed|0 |1
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> If it makes you happy, the following plugs the memory leak:
>
> --- a/gcc/testsuite/gfortran.dg/class_array_7.f03
> +++ b/gcc/testsuite/gfortran.dg/class_array_7.f03
> @@ -56,2 +56,3 @@ program main
> if (trim (print_type ("a", a)) .ne. "a is base_type") call abort
> + deallocate (a)
> end program main
>
> ...
Well, it makes valgrind happy. Is there any connection with PR55207 - Automatic
deallocation of variables declared in the main program?
next prev parent reply other threads:[~2013-07-02 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-30 15:22 [Bug fortran/57762] New: " dominiq at lps dot ens.fr
2013-07-02 9:20 ` [Bug fortran/57762] " burnus at gcc dot gnu.org
2013-07-02 9:43 ` dominiq at lps dot ens.fr [this message]
2013-07-22 11:03 ` janus at gcc dot gnu.org
2013-07-22 17:05 ` burnus at gcc dot gnu.org
2013-07-22 17:05 ` burnus 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-57762-4-Du4u23l8Vi@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).