Slow build

Slow build

[Benjamin Modra]

Three full days to build gcc and its still running.. Does this seem excessive??  
Cygwin on XP @ 3GHz, nothing else running, web disconnected, idle processor.  Are all unix installs like this? 
-Ben



      ____________________________________________________________________________________
Access Yahoo!7 Mail on your mobile. Anytime. Anywhere.
Show me how: http://au.mobile.yahoo.com/mail

Slow Build

[Benjamin Modra]

Hi,
Thanks for all of your responses.  In the end it just turned out I had underestimated the size required for the build .. there was only 100MB left on the the hard drive when it finally completed (5 1/5days - is that a record?).  

Many thanks, Ben



      ____________________________________________________________________________________
Access Yahoo!7 Mail on your mobile. Anytime. Anywhere.
Show me how: http://au.mobile.yahoo.com/mail

Re: Slow build

[Dr. David Kirkby]

Kai Ruottu wrote:
> Dr. David Kirkby wrote:
> 
>> Bill McEnaney wrote:
>>> My Sunblade 100 takes almost 20 hours to build gcc with the machine's
>>> 500 MHz UltrSPARC-II processor and its 64-bit bus.  So to build that
>>> software, I usually launch a batch process with the "batch" command.
>>
>> I just done it in 37 minutes on a Sun T5240, using 'make -j 100'. I 
>> could have probably pushed it a bit harder too, as the machine has 128 
>> hardware threads. This used C, C++ and Fortran.
>>
>> This was for the 'gcc-4.4.1-RC-20090715' snapshot, which I'm going to 
>> test, but I doubt gcc 4.4.0 would be too different.
> 
> Maybe someone could define what the "build gcc" means here... Even in a
> slow 550 MHz P-III PC with Fedora 8 the GCC build for C and C++ took
> only 1 h 17 minutes... Some kind of multi-stage build with several
> builds for GCC?  Not just producing a GCC with the current production
> GCC?  Like with a crosscompiler...
> 
> 

This took 37 minutes on a 16-core machine with 1167 MHz CPUs.

$ gcc -v
Using built-in specs.
Target: sparc-sun-solaris2.10
Configured with: ../gcc-4.4.1-RC-20090715/configure 
--prefix=/usr/local/gcc-4.4.1-RC-20090715-sun-linker 
--with-as=/usr/ccs/bin/as --without-gnu-as --with-ld=/usr/ccs/bin/ld 
--without-gnu-ld --enable-languages=c,c++,fortran 
--with-mpfr-include=/usr/local/include --with-mpfr-lib=/usr/local/lib 
--with-gmp-include=/usr/local/include --with-gmp-lib=/usr/local/lib
Thread model: posix
gcc version 4.4.1 20090715 (prerelease) (GCC)


using C, C++ and Fortran.

Basically I did:

$ ../gcc-4.4.1-RC-20090715/configure 
--prefix=/usr/local/gcc-4.4.1-RC-20090715-sun-linker 
--with-as=/usr/ccs/bin/as --without-gnu-as --with-ld=/usr/ccs/bin/ld 
--without-gnu-ld --enable-languages=c,c++,fortran 
--with-mpfr-include=/usr/local/include --with-mpfr-lib=/usr/local/lib 
--with-gmp-include=/usr/local/include --with-gmp-lib=/usr/local/lib
$ make -j 100

This particular machine is capable of very good performance, but it is 
ill-suited to serial tasks like this. Although parts of the gcc build 
can be done in parallel, a lot of it seems to be done serially.

dave

Re: Slow build

[Kai Ruottu]

Kai Ruottu wrote:
> Dr. David Kirkby wrote:
> 
>> This was for the 'gcc-4.4.1-RC-20090715' snapshot, which I'm going to 
>> test, but I doubt gcc 4.4.0 would be too different.
> 
> Maybe someone could define what the "build gcc" means here... Even in a
> slow 550 MHz P-III PC with Fedora 8 the GCC build for C and C++ took
> only 1 h 17 minutes...

I forgot to tell that I tried the gcc-4.4-20090714 snapshots for a
32-bit Linux/x86 target (not the $build & $host). Single build for
'gcc', 'libgcc', 'libstdc++' etc.

Re: Slow build

[Kai Ruottu]

Dr. David Kirkby wrote:

> Bill McEnaney wrote:
>> My Sunblade 100 takes almost 20 hours to build gcc with the machine's
>> 500 MHz UltrSPARC-II processor and its 64-bit bus.  So to build that
>> software, I usually launch a batch process with the "batch" command.
> 
> I just done it in 37 minutes on a Sun T5240, using 'make -j 100'. I 
> could have probably pushed it a bit harder too, as the machine has 128 
> hardware threads. This used C, C++ and Fortran.
> 
> This was for the 'gcc-4.4.1-RC-20090715' snapshot, which I'm going to 
> test, but I doubt gcc 4.4.0 would be too different.

Maybe someone could define what the "build gcc" means here... Even in a
slow 550 MHz P-III PC with Fedora 8 the GCC build for C and C++ took
only 1 h 17 minutes... Some kind of multi-stage build with several
builds for GCC?  Not just producing a GCC with the current production
GCC?  Like with a crosscompiler...

Re: Slow build

[Dr. David Kirkby]

Bill McEnaney wrote:
> My Sunblade 100 takes almost 20 hours to build gcc with the machine's
> 500 MHz UltrSPARC-II processor and its 64-bit bus.  So to build that
> software, I usually launch a batch process with the "batch" command.
> 
> Bill


I just done it in 37 minutes on a Sun T5240, using 'make -j 100'. I 
could have probably pushed it a bit harder too, as the machine has 128 
hardware threads. This used C, C++ and Fortran.

This was for the 'gcc-4.4.1-RC-20090715' snapshot, which I'm going to 
test, but I doubt gcc 4.4.0 would be too different.


Dave

Re: Slow build

[Michael Haubenwallner]

On Wed, 2009-07-15 at 14:56 -0600, Bill McEnaney wrote:
> My Sunblade 100 takes almost 20 hours to build gcc with the machine's
> 500 MHz UltrSPARC-II processor and its 64-bit bus.  So to build that
> software, I usually launch a batch process with the "batch" command.

Sometimes it also depends on the shell being used. On some AIX for
example (c,c++ only), using /bin/sh (the default) it takes >24 hours,
compared to ~1.5 hours when using bash (CONFIG_SHELL=/path/to/bash).

/haubi/

> 
> Bill
> > 
> > Three full days to build gcc and its still running.. Does this seem
> excessive??  
> > Cygwin on XP @ 3GHz, nothing else running, web disconnected, idle
> processor.  Are all unix installs like this? 
> > -Ben
> > 
> > 
> > 
> >      
> ____________________________________________________________________________________
> > Access Yahoo!7 Mail on your mobile. Anytime. Anywhere.
> > Show me how: http://au.mobile.yahoo.com/mail
> > 
> > 
> 
> ________________________________________________________________
> Please visit a saintly hero:
> http://www.jakemoore.org

Re: Slow build

[Tim Prince]

Bill McEnaney wrote:
> My Sunblade 100 takes almost 20 hours to build gcc with the machine's
> 500 MHz UltrSPARC-II processor and its 64-bit bus.  So to build that
> software, I usually launch a batch process with the "batch" command.
> 
> Bill
>> Three full days to build gcc and its still running.. Does this seem
> excessive??  
>> Cygwin on XP @ 3GHz, nothing else running, web disconnected, idle
> processor.  Are all unix installs like this? 
>> -Ben
>>
It took about 7 hrs to build gcc with configure --enable-languages='c c++
fortran' --disable-shared... with make -j 2 on my 2Ghz core 2 laptop, with
McAfee firewall.  It's about an hour on my Pentium D XPSP3 with make -j 4,
clamav but no firewall.  No way do you want to build other languages if
you care about time.  Testsuite takes about 2 days on the Pentium D.

Re: Slow build

[Bill McEnaney]

My Sunblade 100 takes almost 20 hours to build gcc with the machine's
500 MHz UltrSPARC-II processor and its 64-bit bus.  So to build that
software, I usually launch a batch process with the "batch" command.

Bill
> 
> Three full days to build gcc and its still running.. Does this seem
excessive??  
> Cygwin on XP @ 3GHz, nothing else running, web disconnected, idle
processor.  Are all unix installs like this? 
> -Ben
> 
> 
> 
>      
____________________________________________________________________________________
> Access Yahoo!7 Mail on your mobile. Anytime. Anywhere.
> Show me how: http://au.mobile.yahoo.com/mail
> 
> 

________________________________________________________________
Please visit a saintly hero:
http://www.jakemoore.org

Re: Slow build

[Dennis Clarke]

>
> Three full days to build gcc and its still running.. Does this seem
> excessive??
> Cygwin on XP @ 3GHz, nothing else running, web disconnected, idle
> processor.  Are all unix installs like this?
> -Ben

no way .. that should be about 3 hours .. maybe.

Dennis