Having problems with the Gentoo Handbook? If you're still working your way through it, or just need some info before you start your install, this is the place. All other questions go elsewhere.
LinuxMan wrote:No. Need -march=athlon64 -msse3 . With these CFLAGS build 32bit executable but with optimizations for athlon64
you're right as "-march=athlon64" is like -"mtune=athlon64 -mmmx msse{,2,3} -m3dnow{,ext}"
Now I fscking wonder if "-mtune={athlon-xp,athlon64}" are similar or if alignements variables changes, and in this case, wich one works best for a 32 bit install (or multilib with -m32).
For now I put CFLAGS="-O2 -march=athlon-xp -pipe -msse2 -msse3" and I'm pretty happy with them. I have no need for all the optimization on this world. This should be enough and stable. I found many things that didn't compile with athlon64 and I was getting sick of it. That's why I'm doing this in the first place.
If you're using a 32bits kernel, DON'T set march=k8 or march=athlon64, you will generate 64bits progs and they won't run. As said before, the best is -march=athlon-xp with the corrects switches.
Last edited by CaptainDangeax on Sun Jun 11, 2006 6:30 pm, edited 1 time in total.
the map is not the territory.
Military plans are at best 50% reliable; if more, war would only have winners.
Athlon64 X2 4200+, Gigabyte s969 NForce3 Mainboard, 1GB Ram, NVidia 6600 GT 128MB graphic card, Gentoo 2005.1 for X86_64
CaptainDangeax wrote:If you're using a 32bits kernel, DON'T set march=k8 or march=athlon64, you will generate 64bits progs and they won't run. As said before, the best is -march=athlon-xp with the corrects switches.
Actually, you can. If GCC was built to build for i686 (or whatever x86 you put), it will only build those. I have a 32bit system with march=athlon64, and it works fine.
Though, athlon64 was only introduced in GCC 3.4, but since 3.4 is now in the stable tree...