On Sun, 2005-09-18 at 14:34 -0700, Mark Knecht wrote: > On 9/18/05, maxim wexler <[EMAIL PROTECTED]> wrote: > <SNIP> > > flags : fpu vme de pse tsc msr pae mce cx8 > > apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr > > sse sse2 syscall nx mmxext 3dnowext 3dnow > <SNIP> > > So Walter's point would be that you could add > > mmx mmxext sse sse2 3dnow 3dnowext > > to your use flags, either globally in your make.conf file or for > specific packages in package.use. Adding these flags will enable clode > within the program being emerged specifically supporting those > features. > > My point was that without adding these flags to the compile options > (CXFLAGS) in make.conf I'm not clear that adding the flags in the USE > section of make.conf does anything to generate actual sse or mmx code. > > I'd like to hear from some folks who really understand how gcc works > about this. It's confused me for quite awhile. > > Thanks, > Mark
It is not difficult to figure out what CPU flags to add into an mplayer build. If you get it wrong then mplayer tells you at the start of its output (just run mplayer with no files to play): [EMAIL PROTECTED] ~ $ mplayer MPlayer 1.0pre6-3.3.5-20050130 (C) 2000-2004 MPlayer Team CPU: Advanced Micro Devices Athlon Thunderbird (Family: 6, Stepping: 2) Detected cache-line size is 64 bytes MMX supported but disabled MMX2 supported but disabled 3DNow supported but disabled 3DNowExt supported but disabled CPUflags: MMX: 0 MMX2: 0 3DNow: 0 3DNow2: 0 SSE: 0 SSE2: 0 Compiled for x86 CPU with extensions: ============== (My USE flags are not correctly set up because I just did a GRP install to get this system up and running in quick time). However you will see that MMX, MMX2, 3Dnow and 3DNowExt are supported by mplayer but not compiled into this binary. All of them have appropriate USE flags, which can be seen from "emerge -pv mplayer" The mplayer emerge changes your CFLAGS to suit itself. > -- gentoo-user@gentoo.org mailing list
