-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 04 June 2003 08:35, Gerard Beekmans wrote: > On June 3, 2003 11:09 pm, you wrote: > > 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. > > Be prepared for extra problems with gcc-3.3 too.
probably not in KDE, though, especially if you are compiling KDE 3.1.2 or CVS HEAD. reason being is that many of the developers run gcc-cvs on their development machines, and many of us are using gcc 3.3 right now. and yes, this is largely because of the speed improvements Gerard noted. a few nights ago on IRC we benchmarked it to be "only" 137% slower than gcc 2.95.x when compiling the same C++ code (various bits of KDE). this is a remarkable imporvement over 3.2. =) - -- Aaron J. Seigo GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE: The 'K' is for 'kick ass' http://www.kde.org http://promo.kde.org/3.1/feature_guide.php -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+3mYA1rcusafx20MRAlsVAJ4oGgK4lKalltbXegfiF9dIejU3igCeN158 iLodpq41kwol1MBFW3l8hG4= =MjCN -----END PGP SIGNATURE-----
