public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Pandu Poluan" <Pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: RE: [gentoo-user] CFlags for CPU
Date: Wed, 27 Jul 2011 21:52:07 +0700	[thread overview]
Message-ID: <Z0thlVPNHDcM.j3pbLHQg@mail.poluan.info> (raw)

-original message-
Subject: Re: [gentoo-user] CFlags for CPU
From: Andy Wilkinson <drukargin@gmail.com>
Date: 2011-07-27 21:09

>Another good trick I've found on the forums is to run:
>
>$ gcc -### -e -v -march=native /usr/include/stdlib.h
>
>The last line of output will include the various CFLAGS that
>-march=native picks.  In my case (Phenom II 955):
>
> "/usr/libexec/gcc/x86_64-pc-linux-gnu/4.4.5/cc1" "-quiet"
>"/usr/include/stdlib.h" "-D_FORTIFY_SOURCE=2" *"-march=amdfam10"
>"-mcx16" "-msahf" "-mpopcnt"* "--param" "l1-cache-size=64" "--param"
>"l1-cache-line-size=64" "--param" "l2-cache-size=512" "-mtune=amdfam10"
>"-quiet" "-dumpbase" "stdlib.h" "-auxbase" "stdlib" "-o"
>"/tmp/ccR1PlNZ.s" "--output-pch=/usr/include/stdlib.h.gch"
>
>I typically use -march=native when I don't need to worry about distcc,
>or the options from that output that start with "-m".

Hey, that's a nice trick! Thanks for re-sharing :)

That said, I usually *can't* use -march=native because all my Gentoo systems are virtualized servers, running on top of XenServer, which itself runs on heterogenous server boxes (all Intel).

So, I purposefully limit myself to "-march=nocona".

(I did raise an explicit point about -march parameter in my Gentoo-Wiki article)

Rgds,
--
FdS Pandu E Poluan
~ IT Optimizer ~

Sent from Nokia E72-1




             reply	other threads:[~2011-07-27 14:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27 14:52 Pandu Poluan [this message]
  -- strict thread matches above, loose matches on Subject: below --
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-26 18:59 ` Alan McKinnon
2011-07-26 18:59 ` Mark Knecht
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

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=Z0thlVPNHDcM.j3pbLHQg@mail.poluan.info \
    --to=pandu@poluan.info \
    --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