(Btw, I was expecting a few issues with advanced instruction sets like sssse3 and sse4aaaaa111 being absent from my athlon, but so far all is good. Including mplayer and stuff. Its a different experience from my first experience when I once compiled with march=pentium3 and it gave problems with a p2 class celeron. The second time, I was happily able to run march=pentium4 gentoo on all my machines ranging from my athlon, sempron to core duo and core2 duo. This time, I first used march=nocona, and when it went good, I was brave to try march=core2 on this older athlon.)
Also, as a side note, it has been mentioned many times that Gentoo is not just for ricers. I use it mainly because of its clean and elegant management. (On that note, other distros are yet to come up with something like 'eselect opengl' which can for example make switching graphics easy.) Portage is a gem like APT. Its sad that as mentioned in other forum posts too, that new portage features like updating by git and package sets get no coverage while codenames for ubuntu and fedora are debated.
And the other thing about Gentoo is its stability and system consistency. There are no missing libraries / conflicts on a good gentoo system. Sure all distros can do that, but what requires a effort in them is natural in gentoo. The amount of dev packages one needs to install when occasionally compiling even a small 3rd party package is sometimes nagging in other distros.
And one last thing. In my experience, for most packages, there is no difference in speed between debian i386 packages and super optimized gentoo packages. In fact, mostly debian feels much lighter.
Hope I didn't hijack this thread .
Really, SSE2+ support is only going to affect a few applications anyway, and they've probably got special flags and optimizations setup within the ebuild or program. I'm pretty sure MPlayer, for example, contains lots of manual assembly code and detects what CPU you have at runtime and picks it's fastest paths available.
Last edited by smitty3268; 03-11-2009 at 03:59 AM.
Premature optimization is the root of all evil.
You gentoo users don't test whether it actually gives you any gain...
Overly generalised. Just about all gentoo-ers know that you should not over-optimize.
I use both Gentoo and Ubuntu, and for my dev-stations I always go for gentoo, since I don't get that library hell that is any other distribution...
Does "Parallel" means code generation that utilize multiple threads (TFA talks about "better performance on multi-core systems", so I assume multiple threads must be involved here) or better detecting loops that can be computed in parallel using SIMD instructions?
If first case is true, does compiler care about cost of creating/killing threads on specific OS?
+1Also, as a side note, it has been mentioned many times that Gentoo is not just for ricers.
a distribution that allows you to dynamically alter package dependencies (while resolving dependencies) according to your needs is not something you come across everyday. its package manager also transparently handles binary, from-source or development snapshot (from git,svn,hg,darcs,cvs, etc) packages in the same manner.
The only tricky thing is to find the correct options for the kernel. Compiling a kernel with only the options you need is always a nightmare.
The rest of installation is really easy, and, with a Core2Quad, really fast...
I hope seeing soon the GCC4.4 on Gentoo, which is one of the rare distro to be able to handle that optimization, as other generic distro are compiled for generic i586...