On Friday 07 July 2006 17:31, Martin Schlemmer wrote: > As I pointed out on irc (to clarify), its still an issue even with > gcc-3.4.6. Its just well enough filtered, and as Mike pointed out, they > 'fixed' it in 3.4.5 via specs, and 3.4.6 by backporting patches from > 4.0.1 I think. For what I know, the last issue was fixed with 3.3/3.4, so this sounds new to me. That said, I think this is up to now the only point that would make me rethink over this whole idea. For a pure simple and practical problem.
> I did not imply this as far I know, and if it seemed that way, I can > only say that I assumed that newer guys had the advantage of most > ebuilds filtering or -mno-sse/whatever for known broken stuff Probably, but never assume that gentoo is the first experience for everyone ;) I had my own share of GCC problems way before, and I remember how much shit GCC 3.2 created, 3.3 compared to it was a different order of magnitude: it worked. > I'd say only 4.0.1 and upwards really solved most of those issues, > especially the long comming sse one. Maybe because SSE wasn't that widespread in the past, I remember most issues to be related to MMX/3Dnow! extensions mainly, a part a big one with -msse that I thought dead with GCC 3.3, but I might be mistaken on that then, and I beg you pardon in that case. Of course there's the usual -mfpmath=sse that do cause problems on 32-bit systems (although it's the default on 64-bit). -- Diego "Flameeyes" Pettenò - http://farragut.flameeyes.is-a-geek.org/ Gentoo/Alt lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE
pgpvc4mXWJpWb.pgp
Description: PGP signature
