Gerard Beekmans said: > > If you're not doing so yet, you may want to use GCC-3.3 to compile things > like > KDE. Garbage collection and other areas have improved heuristics which > greatly improve time needed for C++ projects. I've cut my QT time in half > using gcc-3.3. Part of these slow compile times with gcc stem from the > fact > that GCC has a lot of old code that stem from the days when Richard > Stallman > needed a compiler (gcc-1.0 was born) and was optimized for that era's > hardware (64 KB RAM) and a lot of that code is still in GCC. Hardware has > changed and GCC hasn't been the most optimal. Things are changing though > (slowly but surely). > > Here some articles I wrote on this subject: > > GCC-3.3-CVS (a little while before the actual GCC-3.3 release) Performance > Comparison to GCC-3.2.1 > http://tools.devchannel.org/article.pl?sid=03/03/05/1521240&mode=thread&tid=39 > > And Interview I did with Mark Mitchell (GCC's release manager): > http://tools.devchannel.org/article.pl?sid=03/02/21/024211&mode=thread&tid=39 > > In case you don't care to read the articles, the rundown is this: > On my P4-2.2 Ghz, 512 MB RAM QT takes about 20-25 minutes less with > gcc-3.3-cvs at the time (I'm writing a follow-up to test the actual > gcc-3.3 > performance soon). Not much maybe, but if you throw KDE into the loop, you > can easily save a couple of hours.
Thanks for the information :) I haven't tried GCC 3.3 yet, still running on GCC 3.2.2 I'll give it a try on my next KDE upgrade and see how it does. Cheers, -- Trevor Lauder Web: http://www.thelauders.net E-Mail: [EMAIL PROTECTED] Resume: http://www.thelauders.net/resume/ Gentoo Powered "Any intelligent fool can make things bigger and more complex... It takes a touch of genius -- and a lot of courage to move in the opposite direction." -- Albert Einstein
