From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 904 invoked by alias); 14 Nov 2007 16:57:59 -0000 Received: (qmail 845 invoked by alias); 14 Nov 2007 16:57:49 -0000 Date: Wed, 14 Nov 2007 16:57:00 -0000 Message-ID: <20071114165749.844.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: "dberlin at dberlin dot org" 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: 2007-11/txt/msg01296.txt.bz2 ------- Comment #33 from dberlin at gcc dot gnu dot org 2007-11-14 16:57 ------- Subject: Re: Inordinate compile times on large routines On 14 Nov 2007 13:37:54 -0000, lucier at math dot purdue dot edu wrote: > > > ------- Comment #31 from lucier at math dot purdue dot edu 2007-11-14 13:37 ------- > Subject: Re: Inordinate compile times on large routines > > To answer Steven's original question, here is a run with > > euler-20% /pkgs/gcc-mainline/bin/gcc -v > Using built-in specs. > Target: x86_64-unknown-linux-gnu > Configured with: ../../mainline/configure --prefix=/pkgs/gcc-mainline > --enable-languages=c --enable-checking=release --with-gmp=/pkgs/ > gmp-4.2.2 --with-mpfr=/pkgs/gmp-4.2.2 > Thread model: posix > gcc version 4.3.0 20071026 (experimental) [trunk revision 129664] (GCC) > > Memory usage peaked at 10.3GB (just from monitoring top). > Any idea where? None of the numbers below give any interesting suspects, IMHO. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26854