On 19 December 2012 16:58, Dennis Clarke wrote: > >> On 19 December 2012 04:32, Dennis Clarke wrote: >> > >> > That went very well and the compile took a nice long time, even on a >> quad core opteron : >> > >> > real 12255.97 >> > user 10349.35 >> > sys 1565.99 >> >> Presumably this is without -jN? Why would you want to do that? The >> fact it's a quad-core is irrelevant if you only use one core. > > Depends on how much trust you place in -jX for X>1 and in my case, not much, yet. Why? > I am not in a rush, I have a few machines that take well over 168 hours to do a bootstrap and then a testsuite run. To me it is just a process sitting on a back burner simmering and I am fine with that. > > As a fine example .. we have a testsuite run which just completed on this 2.6 GHz Opteron like so : > > http://gcc.gnu.org/ml/gcc-testresults/2012-12/msg01762.html > > > sedna $ /usr/bin/time -p nice -n +19 gmake -k check > . > . > . > real 23347.63 > user 14833.37 > sys 7920.38 > > Six and a half hours on a 3 GHz Opteron. Not pretty but it works. The testsuite is embarrassingly parallel.
