| 1 |
On Dec 19, 2011 1:18 PM, "Dale" <rdalek1967@×××××.com> wrote: |
| 2 |
> |
| 3 |
> Pandu Poluan wrote: |
| 4 |
>> |
| 5 |
>> |
| 6 |
>> Kind of like what I always do when I switch from -march=nocona to |
| 7 |
-march=native. (Usually I use -march=nocona to ensure seamless VM migration |
| 8 |
on my XenServer-equipped boxen, but for some VMs, i.e., those requiring me |
| 9 |
to wring out every last drop of performance, I go native.) |
| 10 |
>> |
| 11 |
>> That said, if you want to experience fully the "GCC Graphite" |
| 12 |
optimizations, you'll also want to do emerge -ev ;-) |
| 13 |
>> |
| 14 |
>> Rgds, |
| 15 |
>> |
| 16 |
> |
| 17 |
> |
| 18 |
> Is Graphite worthwhile on a desktop system or is it better suited for |
| 19 |
servers or both? I found this but still not sure what it is intended for: |
| 20 |
> |
| 21 |
> http://gcc.gnu.org/wiki/Graphite/4.5 |
| 22 |
> |
| 23 |
> Are there any reasons to leave this be for a while? You know, bugs or |
| 24 |
packages that don't work with it? |
| 25 |
> |
| 26 |
|
| 27 |
In my experience, I've never encountered any bugs due to graphite. And I've |
| 28 |
"graphite-ed" 4 production servers, including 2 firewalls, 1 DNS server, |
| 29 |
and 1 mail server. |
| 30 |
|
| 31 |
Of course, YMMV. |
| 32 |
|
| 33 |
Rgds, |
Archives