From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] A tale of computing thud and blunder
Date: Mon, 19 Dec 2011 10:37:45 -0600 [thread overview]
Message-ID: <CAEH5T2O1Xd=46G+-K4mMYEVdDTpc2EdnuRX903_L_mLHFUO5fQ@mail.gmail.com> (raw)
In-Reply-To: <4EEED697.4030000@gmail.com>
On Mon, Dec 19, 2011 at 12:15 AM, Dale <rdalek1967@gmail.com> wrote:
> Pandu Poluan wrote:
>>
>>
>> Kind of like what I always do when I switch from -march=nocona to
>> -march=native. (Usually I use -march=nocona to ensure seamless VM migration
>> on my XenServer-equipped boxen, but for some VMs, i.e., those requiring me
>> to wring out every last drop of performance, I go native.)
>>
>> That said, if you want to experience fully the "GCC Graphite"
>> optimizations, you'll also want to do emerge -ev ;-)
>>
>> Rgds,
>>
>
>
> Is Graphite worthwhile on a desktop system or is it better suited for
> servers or both? I found this but still not sure what it is intended for:
>
> http://gcc.gnu.org/wiki/Graphite/4.5
>
> Are there any reasons to leave this be for a while? You know, bugs or
> packages that don't work with it?
I used it for @world and ran into a couple times when things were
broken with it enabled... Don't really remember specifics. I didn't
notice any perceivable speed difference, so I stopped using it just to
simplify things in the future. :)
In general,I have changed my CFLAGS to be less aggressive over the
past years. I started with the most aggressive optimizations, and
using -march=whatever... At some point I researched compile times for
different optimizations and realized some packages were taking tens of
minutes longer to compile! Surely whatever potential speed increase of
-O3 vs -O2 was not going to give me tens of minutes cumulatively. If
there is a package that really benefits from some specific
optimization (and doesn't already set those flags itself in the
ebuild), I'll set the CFLAGS for that individual package but leave the
rest of world very simplistic.
Same with -march, I've gone to using -mtune instead, after having to
move hard drives into a system with different CPU feature set. And for
virtual machines (in hosts I don't control, especially), they could be
migrated to some other machine without my knowledge, and i don't want
it to stop working if that happens.
next prev parent reply other threads:[~2011-12-19 16:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 21:07 [gentoo-user] -march=native is *EXTREMELY* conservative Walter Dnes
2011-12-17 21:53 ` 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 [this message]
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='CAEH5T2O1Xd=46G+-K4mMYEVdDTpc2EdnuRX903_L_mLHFUO5fQ@mail.gmail.com' \
--to=paul.hartman+gentoo@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