public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] CFlags for CPU
Date: Tue, 26 Jul 2011 11:59:25 -0700	[thread overview]
Message-ID: <CAK2H+edS71xQmLooSGGWTSh4HxhZG1HcniziZb5LQUQwzZkavA@mail.gmail.com> (raw)
In-Reply-To: <4E2F253E.1000508@alokat.org>

On Tue, Jul 26, 2011 at 1:36 PM, Alokat <mailing@alokat.org> wrote:
> Hi folks,
>
> I'm wondering what kind of cpu-type I should use?
>
> cat /proc/cpuinfo
> ..............
>
> processor       : 1
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 15
> model name      : Intel(R) Core(TM)2 Duo CPU     L7100  @ 1.20GHz
> stepping        : 11
> cpu MHz         : 1197.065
> cache size      : 4096 KB
> physical id     : 0
> siblings        : 2
> core id         : 1
> cpu cores       : 2
> apicid          : 1
> initial apicid  : 1
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 10
> wp              : yes
> 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 syscall nx lm
> constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64
> monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm ida dts tpr_shadow
> vnmi flexpriority
> bogomips        : 2394.01
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 36 bits physical, 48 bits virtual
> power management:
>
> ..............
>
> After a short research on this website:
> http://gcc.gnu.org/onlinedocs/gcc-4.6.1/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options
>
> I guess core2 is the right one?
> Is that true?
>
> Regards,
> alokat
>

Or let gcc figure it out using

-march=native

which is what I eventually did:

# Please consult /usr/share/portage/config/make.conf.example for a more
# detailed example.
CFLAGS="-O2 -march=native -pipe"
#Safe CFlags for the Core-i7 (web info) saved for reference
#CFLAGS="-march=core2 -msse4 -mcx16 -msahf -O2 -pipe"
CXXFLAGS="${CFLAGS}"
# WARNING: Changing your CHOST is not something that should be done lightly.
# Please consult http://www.gentoo.org/doc/en/change-chost.xml before changing.
CHOST="x86_64-pc-linux-gnu"


HTH,
Mark



  parent reply	other threads:[~2011-07-26 19:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26 20:36 [gentoo-user] CFlags for CPU Alokat
2011-07-26 18:58 ` Michael Mol
2011-07-27  0:58   ` Bill Kenworthy
2011-07-27  3:08     ` [gentoo-user] " Nikos Chantziaras
2011-07-26 18:59 ` [gentoo-user] " Alan McKinnon
2011-07-26 18:59 ` Mark Knecht [this message]
2011-07-26 19:02 ` Paul Hartman
2011-07-26 22:01   ` Mick
2011-07-26 22:15     ` Paul Hartman
2011-07-26 19:22 ` pk
2011-07-27 14:09   ` Andy Wilkinson
2011-07-27 14:34     ` Kfir Lavi
2011-07-27 16:13       ` Kfir Lavi
2011-07-27 18:32         ` Mick
2011-07-27 20:24           ` Mark Knecht
2011-07-27 20:56             ` Mick
2011-07-27 21:11           ` pk
2011-07-28  9:40           ` Kfir Lavi
2011-07-28  9:46             ` Helmut Jarausch
2011-07-28  9:51               ` Kfir Lavi
2011-07-28 10:01                 ` Helmut Jarausch
  -- strict thread matches above, loose matches on Subject: below --
2011-07-27 14:52 Pandu Poluan

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=CAK2H+edS71xQmLooSGGWTSh4HxhZG1HcniziZb5LQUQwzZkavA@mail.gmail.com \
    --to=markknecht@gmail.com \
    --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