From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-430451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 28872 invoked by alias); 24 Sep 2013 08:03:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 28814 invoked by uid 48); 24 Sep 2013 08:03:35 -0000
From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/55469] memory leak on read with istat.ne.0
Date: Tue, 24 Sep 2013 08:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: Joost.VandeVondele at mat dot ethz.ch
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: burnus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-55469-4-v7PANz79Im@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55469-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55469-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-09/txt/msg01691.txt.bz2

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

--- Comment #10 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> ---
This bug is a bit of showstopper for doing automatic leak testing with
gperftools (essentially all our regtests have a non-zero error code with this
leak being detected). Any chance to revive one of the patches posted ?