Luca Barbato wrote: > Alternatives: > > - as PPC we provide a default cflags & use tuned per certain cpu > families using profiles, amd64 could provide a nocona profile that bans > 3dnow* useflags.
Not really. There are athlon64s and opterons with and without sse3 support. The users who have an sse3-enabled CPU mostly stick -msse3 into their CFLAGS, as they expect the flag to do what it says. The problem is even worse for x86: You'd have to provide own profiles for: * i386 * pentium-mmx,k6 * athlon xp,pentium3 * pentium4,athlon64/opteron (starting from 'Paris' core),celeron (starting from 'willamette' core) * celeron D/M, core solo/duo,core 2 duo, core 2 extreme,athlon64 (starting from venice stepping E3 or san diego stepping E4), athlon64 X2, athlon64 FX (starting from san diego stepping E4), sempron (starting from palermo stepping E3), pentium4 (starting from 'prescott') etc... and now you want to let your pentium4(paris)-server, which is running 24/7, compile a binpkg for your pentium4(prescott), using SSE3 have fun 8-) > - as before but provide an eclass that uses flameeyes infrastructure to > warn about possible mismatch between what the cflags could do and what > you expect to obtain eg: -mcpu=nocona use 3dnow would issue a warning > and disable it I'm not sure whether I understand this correctly. If we use flameeyes logic anyway, why keeping the use flags? -- Kind Regards, Simon Stelling Gentoo/AMD64 Developer -- gentoo-dev@gentoo.org mailing list
