From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28005 invoked by alias); 25 Apr 2008 08:10:46 -0000 Received: (qmail 27772 invoked by uid 48); 25 Apr 2008 08:10:01 -0000 Date: Fri, 25 Apr 2008 08:10:00 -0000 Message-ID: <20080425081001.27770.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/35892] gfortran lost memory blocks In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "KnowlesPJ at Cardiff dot ac dot uk" 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: 2008-04/txt/msg01792.txt.bz2 ------- Comment #22 from KnowlesPJ at Cardiff dot ac dot uk 2008-04-25 08:10 ------- Yes, this was the silver bullet. With Using built-in specs. Target: i386-apple-darwin9.2.2 Configured with: ../configure --prefix=/opt/gcc Thread model: posix gcc version 4.4.0 20080424 (experimental) (GCC) we now get through the regression tests on our code that were failing before. Thank you to those who have contributed to this - the final piece that was needed for our code (http://www.molpro.net) to work with gfortran on both linux and mac. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35892