From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13568 invoked by alias); 1 Jun 2012 21:08:04 -0000 Received: (qmail 13557 invoked by uid 22791); 1 Jun 2012 21:08:03 -0000 X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 01 Jun 2012 21:07:50 +0000 From: "burnus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/53521] [4.5/4.6/4.7/4.8 Regression] Memory leak with zero-sized array constructor Date: Fri, 01 Jun 2012 21:08: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-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: burnus at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P5 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.5.4 X-Bugzilla-Changed-Fields: Status Resolution Target Milestone Summary Known to fail Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-06/txt/msg00080.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53521 Tobias Burnus changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED Target Milestone|4.6.4 |4.5.4 Summary|[4.5/4.6/4.7 Regression] |[4.5/4.6/4.7/4.8 |Memory leak with zero-sized |Regression] Memory leak |array constructor |with zero-sized array | |constructor Known to fail| |4.8.0 --- Comment #14 from Tobias Burnus 2012-06-01 21:07:49 UTC --- FIXED on the trunk and on all still maintained branches: 4.5, 4.6 and 4.7. (In reply to comment #10) > this fixes the issue I saw for CP2K. From some further tests I > did, I couldn't see any negative side effects. Good to hear. > I had a look at other gcc branches, the patch applies flawlessly to 4.7 and 4.6 > (I did not have a 4.5 branch around). The patch didn't apply directly to 4.5, but replicating the code manually was very simple. > I would be very happy to see it integrated in 4.7.1 and 4.6.4, Note that 4.7.1 will be released soon; I think release-candidate build is due next week.