Martin Schlemmer wrote: > Stupid question though ... does the gcc test thingy list __3dNOW__ on > nocona ? I would think that it does, as there is no -march=nocona (or > whatever) yet.
There is a -march=nocona, and it doesn't define __3dNOW__. > So now you want to instead of fixing the amd64 profiles to be more > flexible, implement something that will give the green light to users on > x86 to use flag combinations, especially on older gcc's that causes > great pain for themselfs and developers ? I don't understand this. Why is '-march=i686 -m3dnow' bad if it results in the same thing as '-march=athlon-xp'? I guess I'm just lacking facts here, so please give me a hint :) -- Kind Regards, Simon Stelling Gentoo/AMD64 Developer -- gentoo-dev@gentoo.org mailing list
