1 |
On Dec 19, 2011 7:20 AM, "Dale" <rdalek1967@×××××.com> wrote: |
2 |
> |
3 |
> Walter Dnes wrote: |
4 |
>> |
5 |
>> It's probably the sum total of the effect of all the flags. I've renamed |
6 |
the thread, to be more accurate. Here's how things went... * right after |
7 |
the install (presumably with generic i686 code) the PC could not handle |
8 |
streaming 1080i video from my HDHomerun TV tuner * I misinterpreted output |
9 |
from gcc diagnostics, and concluded that "march=-native" left several flags |
10 |
disabled that shouldn't be * acting on that (mis)information), I emerged |
11 |
system+world+kernel and found that not only could my system handle 1080i, |
12 |
it could handle a 1080p Youtube clip without problems, after a lot of |
13 |
buffering. My 5 megabit ADSL connection was the limiting factor there. It's |
14 |
supposed to be upgraded to 6 megabits one of these days, for some minor |
15 |
improvement. * I mistakenly thought that it was the additional flags in |
16 |
CFLAGS during the emerge system+world that boosted the video. Actually, the |
17 |
emerge would've done the trick. The lesson from this is that, before doing |
18 |
any benchmarking or heavy-duty usage, one should emerge system+world, to |
19 |
replace the generic code from the install CD with fully optimized code. |
20 |
It's easiest to so right after the initial install, so that there are as |
21 |
few packages to emerge as possible. |
22 |
> |
23 |
> |
24 |
> |
25 |
> That is good advice too. When I do a install, I unpack the tarball and |
26 |
do the normal things and get my make.conf settings done. Since there is |
27 |
very little installed anyway, I do a emerge -ev world. It usually takes |
28 |
only a hour or so depending on the speed of the rig. Thing is, you then |
29 |
have everything compiled with your settings and not the generic ones the |
30 |
tarball had. It also updates anything that needs it too. Even before |
31 |
amd64 came along I did it this way. Lots of people use Intel CPUs but I |
32 |
use AMD. I don't know what the person that made the tarball uses but |
33 |
either way, he has to make it generic so that it will run on ANY CPU. |
34 |
> |
35 |
> I wonder if they should mention this in the docs? It seemed to have made |
36 |
a difference in your case for sure. You went from not being able to play a |
37 |
video to being able to play a HD video. |
38 |
> |
39 |
|
40 |
Kind of like what I always do when I switch from -march=nocona to |
41 |
-march=native. (Usually I use -march=nocona to ensure seamless VM migration |
42 |
on my XenServer-equipped boxen, but for some VMs, i.e., those requiring me |
43 |
to wring out every last drop of performance, I go native.) |
44 |
|
45 |
That said, if you want to experience fully the "GCC Graphite" |
46 |
optimizations, you'll also want to do emerge -ev ;-) |
47 |
|
48 |
Rgds, |