On Sunday 22 June 2003 21:32, Zack Gilburd wrote: > On Sunday 22 June 2003 11:35, Hemmann, Volker Armin wrote: > > Hi, > > > > On Sunday 22 June 2003 09:52, Zack Gilburd wrote: > > > I *think* that gcc-3.3 was mistakenly unmasked by drobbins. > > > > > > avenj also said the tree is VERY unready for gcc-3.3. > > > > > > Also, I think env-update'ing would have been a better choice. > > > > I am using gcc 3.3 for some time now. > > > > I compiled everything, XFREE, glibc, KDE, perl, python, kernel, xine, > > mplayer... with gcc 3.3 and have NO problems since than. > > > > gcc 3.3 is a lot faster than gcc 3.2 and I have less stability problems > > with the same CFLAGS. > > > > Gl�ck Auf > > Volker > > > > > > -- > > [EMAIL PROTECTED] mailing list > > This is so wrong, I don't know where to begin. For one, it's a FACT that > compiling a kernel takes roughly 3x longer than it did with 2.95.x. Not > only does it take longer, but the end kernel comes out about 200KB larger. > Also...
3.0.X was horrible slow, and 3.1 and .3.2 are not better, but gcc 3.3 is in my humple experience the fastest of the gcc-3.x line. It is still slower than 2.95.X but I don't care for such an old compiler. I compared to 3.2.x. > [18:42:39] <avenj> drobbins: did you intend to mark gcc-3.3 ~x86 and unmask > it? > [18:42:48] <avenj> the tree is definitely not very gcc-3.3 ready > > That was yesterday. No offense, but I am going to go what with avenj, a > highly respected and veteran Gentoo dev, over what two ML posters say. I do not recommend gcc 3.3, infact, I am the 'guinea pig' of some friends with gentoo-boxes. I am bleeding edge, they watch my suffering and decide, what they want to try, after a loooooong time of considering... > You guys can risk your systems however you would like, but I won't take my > chances. Not to mention that if you upgrade glibc (and gcc AFAIK), you CAN > NOT downgrade. I had latest glibc with gcc 3.2.3 when I decided to switch over. I read the bugs related to gcc 3.3 and saw, that all problems there where related to -O3. No problem, I never use -O3, because this was not very stable with gcc 3.2, 3.1 and 3.0. KDE 3.1.2 is stable (except one javascrip bug), XFree is stable, my kernels are not crashing, I am able to use xine, ut2003-demo and xmms, I am burning cds, watching tv, using licq, playing lgeneral ( a crash and quitting, was there with former gcc too). I rebuild whole KDE 3.1.2 in less time with gcc 3.3 , than kdelibs-3.1.2 and kdebase-3.1.2 with gcc-3.2.3 Yes, there are some problems. To emerge alsa, I have to edit /usr/src/linux/include/linux/compile.h and nvidia-kernel-tarball needed a little edit, but that were all problems I had. Maybe a lot of apps out there are very unstable with gcc-3.3, maybe I don't have these apps installed, or I am simple a lucky sod. And this are my CFLAGS: CFLAGS="-march=athlon-xp -O2 -pipe -mmmx -m3dnow -msse -mfpmath=sse -fomit-frame-pointer -ftracer" (could be reduced ot -march=athlon-xp -O2 -mfpmath=sse -ftracer -fomit-frame-pointer -pipe, I think, but I am too lazy to touch /etc/make.conf) Gl�ck Auf Volker -- [EMAIL PROTECTED] mailing list
