------- Comment #55 from zadeck at naturalbridge dot com 2008-01-17 22:57 ------- Subject: Re: Inordinate compile times on large routines
lucier at math dot purdue dot edu wrote: > ------- Comment #54 from lucier at math dot purdue dot edu 2008-01-17 22:39 > ------- > Created an attachment (id=14963) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14963&action=view) > --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14963&action=view) > memory details for 131610 > > This is the detailed memory usage for the compiler > > euler-5% /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 --enable-gather-detailed-mem-stats > Thread model: posix > gcc version 4.3.0 20080117 (experimental) [trunk revision 131610] (GCC) > > The maximum memory I observed in top was 10.2 GB. > > Kenny, I can't tell whether your patch from > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34400#c50 > > has been committed; will that improve the situation, too? > > > it could, but it is not the big issue here, the big issue is the size of the def use chains. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26854
