public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/29101] Memory leak in gfortran Date: Tue, 19 Sep 2006 11:26:00 -0000 [thread overview] Message-ID: <20060919112608.8985.qmail@sourceware.org> (raw) In-Reply-To: <bug-29101-6552@http.gcc.gnu.org/bugzilla/> ------- Comment #11 from pault at gcc dot gnu dot org 2006-09-19 11:26 ------- Thanks to Steven's intervention, I can declare this bug well and truly closed. Paul -- pault at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29101
next prev parent reply other threads:[~2006-09-19 11:26 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-09-15 19:59 [Bug libfortran/29101] New: memory leak in libgfortran franke dot daniel at gmail dot com 2006-09-16 1:29 ` [Bug libfortran/29101] " jvdelisle at gcc dot gnu dot org 2006-09-17 20:14 ` [Bug fortran/29101] Memory leak in gfortran jvdelisle at gcc dot gnu dot org 2006-09-18 6:53 ` pault at gcc dot gnu dot org 2006-09-18 7:50 ` pault at gcc dot gnu dot org 2006-09-18 17:15 ` patchapp at dberlin dot org 2006-09-18 19:29 ` pault at gcc dot gnu dot org 2006-09-18 20:20 ` pault at gcc dot gnu dot org 2006-09-18 22:24 ` pault at gcc dot gnu dot org 2006-09-18 22:35 ` steven at gcc dot gnu dot org 2006-09-19 11:05 ` pault at gcc dot gnu dot org 2006-09-19 11:25 ` pault at gcc dot gnu dot org 2006-09-19 11:26 ` pault at gcc dot gnu dot org [this message] 2006-09-19 11:56 ` paulthomas2 at wanadoo dot fr
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=20060919112608.8985.qmail@sourceware.org \ --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).