From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9840 invoked by alias); 6 Jan 2008 22:09:14 -0000 Received: (qmail 9710 invoked by uid 48); 6 Jan 2008 22:08:32 -0000 Date: Sun, 06 Jan 2008 22:15:00 -0000 Message-ID: <20080106220832.9709.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/34683] Fortran FE generated IL pessimizes middle-end IL and analysis In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "jaydub66 at gmail dot com" 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-01/txt/msg00554.txt.bz2 ------- Comment #16 from jaydub66 at gmail dot com 2008-01-06 22:08 ------- I've done some experimenting with older GCC versions I have floating around on my machines: Compiling the test case with both 4.1.2 and 4.2.1 gives an ICE, so I guess we can't exactly call this a regression. But then compiling with older 4.3 trunk builds works much better: I have a version from August 24 of last year, which runs the test case at full -O3 in a perfect 8sec, with 32MB memory usage (that is with --enable-checking=release). And I have two other builds from October 8 and November 9, which both run the test case in about 38s with 85MB mem-usage (they are built with --enable-checking=debug, so this is probably just debugging overhead). At least none of them takes the crazy 800MB of recent builds. To sum up: It seems like trunk versions up to at least November 9 seem to work fine on this test case. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34683