public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] -march=native is *EXTREMELY* conservative
Date: Sat, 17 Dec 2011 16:07:09 -0500	[thread overview]
Message-ID: <20111217210709.GA1740@waltdnes.org> (raw)

  Here's the setup of my secondary machine..  It's a Dell Inspiron
Desktop 530, with 2 gigs of ram, assembled and shipped August 2007.  It
has an Intel Core2 (*NOT* a "Core2 Duo") cpu.  From /proc/cpuinfo...

vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Genuine Intel(R) CPU            2140  @ 1.60GHz
stepping        : 2
cpu MHz         : 1595.660
cache size      : 1024 KB

  Here are 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

  Then I ran "gcc -march=native -Q --help=target" and got a major shock.
It's a long output listing of what -march=native thinks about my cpu.
Here are some relevant items...

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

  It properly identified the cpu as "core2".  But mmx, sse, sse2, sse3
(aka pni), and ssse3 are disabled!!! 

  The reason I dug into this was that I was trying to 1920x1080i
streaming video from my HDHomerun TV tuner box.  I originally used

CFLAGS="-O2 -march=native -fomit-frame-pointer -pipe"

when setting up the system.  It could not handle 1920x1080i streaming TV
video.

  After findinding out about "-native", I changed CFLAGS to...

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

...and emerged system and world and rebuilt the kernel.  Now the onboard
Intel GPU handles 1920x1080i flawlessly.  As a matter of fact, it
handles 1080p flawlessly.

-- 
Walter Dnes <waltdnes@waltdnes.org>



             reply	other threads:[~2011-12-17 21:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-17 21:07 Walter Dnes [this message]
2011-12-17 21:53 ` [gentoo-user] -march=native is *EXTREMELY* conservative Dale
2011-12-17 21:58 ` [gentoo-user] " Nikos Chantziaras
2011-12-18  1:10   ` Walter Dnes
2011-12-18 10:34     ` Walter Dnes
2011-12-18 10:45       ` Nikos Chantziaras
2011-12-18 18:10         ` Andrea Conti
2011-12-19  0:05         ` [gentoo-user] A tale of computing thud and blunder Walter Dnes
2011-12-19  0:17           ` Dale
2011-12-19  5:41             ` Pandu Poluan
2011-12-19  6:15               ` Dale
2011-12-19  6:49                 ` [gentoo-user] " Nikos Chantziaras
2011-12-19  7:21                   ` Dale
2011-12-19 12:49                   ` walt
2011-12-19  8:14                 ` [gentoo-user] " Pandu Poluan
2011-12-19 16:37                 ` Paul Hartman
2011-12-18  1:15 ` [gentoo-user] -march=native is *EXTREMELY* conservative Paul Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111217210709.GA1740@waltdnes.org \
    --to=waltdnes@waltdnes.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox