From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10544 invoked by alias); 10 Jul 2008 17:37:33 -0000 Received: (qmail 9141 invoked by uid 48); 10 Jul 2008 17:36:47 -0000 Date: Thu, 10 Jul 2008 17:37:00 -0000 Message-ID: <20080710173647.9140.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug tree-optimization/26854] Inordinate compile times on large routines In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "lucier at math dot purdue dot edu" 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-07/txt/msg01054.txt.bz2 ------- Comment #70 from lucier at math dot purdue dot edu 2008-07-10 17:36 ------- Created an attachment (id=15893) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15893&action=view) detailed memory stats for trunk revision 137644 These are the detailed memory stats for euler-11% /pkgs/gcc-mainline/bin/gcc -v Using built-in specs. Target: x86_64-unknown-linux-gnu Configured with: ../../mainline/configure --enable-checking=release --with-gmp=/pkgs/gmp-4.2.2/ --with-mpfr=/pkgs/gmp-4.2.2/ --prefix=/pkgs/gcc-mainline --enable-languages=c --enable-gather-detailed-mem-stats Thread model: posix gcc version 4.4.0 20080708 (experimental) [trunk revision 137644] (GCC) applied to this problem, with command line /pkgs/gcc-mainline/bin/gcc -Wall -W -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -ftime-report -fmem-report -c all.i >& mainline-stats-O3 The run time isn't so bad, but the memory usage still peaks at 7.3 gigs. Now that distributions have started shipping 4.2.whatever (Ubuntu 8.04 ships 4.2.3), this problem is showing up more an more as a regression against previous releases of gcc. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26854