Are the things that are automatically enabled for compilation different than the things the USE flags enable?
If these things are automatic, then why have the flags at all?
On 4/30/05, Keith Gable <[EMAIL PROTECTED]
> wrote:
What they're saying is that SSE/SSE2/MMX and so on are automatically applied without the flags. The flags are only there because not every x86 chip supports SSE, SSE2, and so on. On AMD64, the flags are ignored and it's compiled with any of those processor optimizations that it knowingly supports.
If something came out that was AMD64 Generation 2 specific (and wasn't supported by regular AMD64), it'd have a USE flag that only works on AMD64. And you wouldn't want to turn that flag on on a normal AMD64, since it doesn't support it.
Right now, if you compile mplayer, you'll get MMX/SSE/SSE2/3DNOW and all that crap. Just there are no special USE flags for it.--On 4/30/05, Kiawud < [EMAIL PROTECTED]> wrote:On 4/29/05, Ciaran McCreesh < [EMAIL PROTECTED]> wrote:
> On Fri, 29 Apr 2005 16:54:57 +0000 Calvin Spealman
> < [EMAIL PROTECTED]> wrote:
> | i dont understand whats going on here. I thought those flags enabled
> | the use of extended sets of the x86 instruction set, and amd64 chips
> | are in the x86 family, aren't they? and they support those
> | extensions, I'm sure, so what then do those flags do that the amd64
> | can't make use of the flags?
>
I thought that if you 'cat /proc/cpuinfo' it'll show you the flags
that are compatible with your cpu. Is that not accurate for the amd64
chip?
-Hani
--
gentoo-user@gentoo.org mailing list
"Microsoft is a lot better at making money than it is at making good operating systems."
-- Linus Torvalds
