On Sat, 2008-06-21 at 08:10 -0400, Diego Novillo wrote: > On Sat, Jun 21, 2008 at 05:21, Andrew Haley <[EMAIL PROTECTED]> wrote: > > > Kaveh does have a point, Diego. The libjava build regularly finds > > middle-end > > problems that are not revealed by bootstrap testing. > > So does Ada. This is why I have offered keep building it on my nightly > testers. > > IME, bugs found during libjava have been also triggered during > libstdc++ and/or C. Though several folks at the summit mentioned that > they had found bugs triggered only by libjava. > > My point remains that libjava has become a serious problem in the > development cycle of GCC. It takes roughly 3 hours on modern hardware > to finish a GCC bootstrap (with -j2). A significant chunk of which is > taken by libjava. If we could at least reduce the overhead by not > building all of it by default, it would be a huge win.
Some data: with --enable-languages=all,ada --disable-multilib on 4.3.1 release on a 4 Opteron 2.0 GHz cores machine from the compile farm, I got for make bootstrap: -j1 2h18 -j2 1h14 -j4 0h43 -j6 0h42 And for make -k check: -j1 2h18 -j2 1h11 -j4 0h55 -j6 0h44 Without Ada (=all) bootstrap gets down to 1h54 at -j1 so Ada is 0h24, or 17% of =all, without Ada and Java (=c,c++,fortran,objc) it gets down to 1h17 at -j1 so java is 0h37 or 27% of =all. On trunk at -j1 with the same configure my autotester for all,ada get 3h22 boostrap (+1h04, +46%) and 2h52 check (+0h34, +25%). It shows that additional checking on trunk is not cheap (assuming we didn't get much slower since 4.3). The compile farm has three 8 cores machines but I didn't try recently -j8 on them but it should be in the 20-25 minute range with all,ada: http://gcc.gnu.org/wiki/CompileFarm Laurent
