Kumar Golap wrote:
Apologies for not having done my research properly....
In this /specific/ case, you don't have to because the ebuilds and gcc know
that x86_64 CHOST means that mmx etc. ARE supported and they will
hard-enable them (you may not turn them off).
Do you mean that, say, xawtv would have been built with mmx for an
amd64 arch...despite that "equery uses" say its not ? Because that
what confused me....
Thanks
Kumar
There's a difference. Due to your CHOST, the compiler knows what
optimizations are supported by your CPU and will automatically generate
code that makes the best possible use of them. On the other hand, the
"mmx" USE flag's most likely effect is to activate portions of the
program's code that explicitly invoke MMX CPU instructions - for
example, through assembly inlining. I don't know much about 64-bit
systems, so I'd recommend leaving "mmx" masked as per your profile, or
perhaps unmasking it just to test one or two packages for stability, and
then unmasking permanently if you have no problems.
--
gentoo-user@gentoo.org mailing list
