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...
