From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: A tale of computing thud and blunder
Date: Mon, 19 Dec 2011 01:21:08 -0600 [thread overview]
Message-ID: <4EEEE5E4.4030808@gmail.com> (raw)
In-Reply-To: <jcmmol$km0$1@dough.gmane.org>
Nikos Chantziaras wrote:
> On 12/19/2011 08:15 AM, Dale 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 ;-)
>>
>>
>> Is Graphite worthwhile on a desktop system or is it better suited for
>> servers or both?
>
> This isn't something that even remotely has anything to do with
> servers or desktops. Just like -O2 does not magically work better on
> servers.
>
>
Sounds like it may work on both then. That's sort of what I was
thinking but wasn't sure.
>> I found this but still not sure what it is intended for:
>>
>> http://gcc.gnu.org/wiki/Graphite/4.5
>
> It's an optimization that produces faster running executables. Are
> you interested in *how* it works :-)
>
>
From what I read it makes some processes run in parallel instead of
serial or one at a time. Some think it is meaningless but some think it
is awesome. I don't know what to think since I have not used it or
compared the differences.
>> Are there any reasons to leave this be for a while? You know, bugs or
>> packages that don't work with it?
>
> Just like with any other optimization switch, there can be bugs. If
> Gentoo says it doesn't support graphite, then I'd stay away from it
> because Gentoo devs might not listen to your bug reports if you use
> it. I don't know if they support it or not though.
>
That would be another good thing to know. I don't file many bug reports
but if something breaks and it needs one, I do file them. This may be
like good wine. It may need to rest a while longer unless someone else
knows it is supported and works well. I got a good install and I don't
want to break it.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
Miss the compile output? Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"
next prev parent reply other threads:[~2011-12-19 7:22 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 [this message]
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=4EEEE5E4.4030808@gmail.com \
--to=rdalek1967@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