On Fri, Dec 16, 2011 at 01:57:58PM +0000, James wrote

> Find the minimal flags and the optimum CFLAGS settings for 
> your needs. Refine by testing. USE a fast hard drive.....
> Avoid apps that soak up ram. Some video apps are ram_hogs...
> 
> I'd be curious to learn what you finally figure out.

  Here's my current setup.  First the cpu flags...

waltdnes@d530 ~ $ grep flags /proc/cpuinfo
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl
est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts

  And what I've specified in CFLAGS and USE

waltdnes@d530 ~ $ grep "\(CFLAGS\|USE\)" /etc/make.conf
CFLAGS="-O2 -march=native -mfpmath=sse -fomit-frame-pointer -pipe"
CXXFLAGS="${CFLAGS}"
USE="-* X a52 aac bzip2 cxx dga dri exif ffmpeg flac fortran gallium gif
intel jpeg mmx mng mp3 mpeg nptl nptlonly nsplugin offensive ogg opengl
png posix sse sse2 ssse3 theora threads tiff truetype vim-syntax vorbis
win32codecs wmf xcomposite xpm xv xvid zlib"

  One more thing.  I just ran "gcc -march=native -Q --help=target" and
got a major shock.  It's a long output listing of what is/isn't enabled
with -march=native on my cpu.  Here are some relevant items...

-march=                               core2
-mmmx                                 [disabled]
-msse                                 [disabled]
-msse2                                [disabled]
-msse3                                [disabled]
-mssse3                               [disabled]

  It has properly identified the cpu as "core2".  But mmx, sse, sse2,
sse3 (aka pni), and ssse3 are disabled!!!  I'll change my CFLAGS to...

CFLAGS="-O2 -march=native -mmmx -msse -msse2 -msse3 -mssse3 -mfpmath=sse 
-fomit-frame-pointer -pipe"

...and emerge system and world and rebuild the kernel.  Then I'll see
if it helps.  It'll probably be at least an overnight job for each
emerge, if not longer.

-- 
Walter Dnes <waltd...@waltdnes.org>

Reply via email to