1 |
On Tue, Apr 25, 2006 at 01:59:47AM -0700, Duncan wrote: |
2 |
|
3 |
> That's also why I tend to favor -Os and certain other similar |
4 |
> optimizations (I add various register re-use and hot/cold function |
5 |
> reordering flags as well, as the register optimizations will be very good |
6 |
> for amd64, even at the cost of code size, and hot/cold function reordering |
7 |
> regroups functions such that the frequently used ones stay in cache |
8 |
> better, even at the expense of overall code size). Smaller code, given |
9 |
> memory latencies, should be faster code, even if it's less efficient at |
10 |
> the CPU itself, because that much more of the code fits in the next closer |
11 |
> level of cache, that would otherwise be in far slower memory or cache |
12 |
> futher from the CPU. |
13 |
|
14 |
Thats interesting stuff Duncan. I've been looking for details regarding gcc's |
15 |
possible optimizations for AMD64 along with low-level details of what they do. |
16 |
Are you using gcc 3 or 4? Is there much work to be done, porting AMD64 |
17 |
optimizations from 3 to 4's tree stuff? I'd like to read more or know where to |
18 |
find additional info. |
19 |
|
20 |
> That said, performance is one thing, human frustration is an entirely |
21 |
> different thing. Because the (desktop/workstatiion) computer spends most |
22 |
> of its time waiting for human input, an efficient human/computer interface |
23 |
> is a far more important factor than all the others. Of course, one |
24 |
> person's richly efficient interface is another's bloat, making it |
25 |
> virtually impossible to benchmark. |
26 |
> |
27 |
> The reason I suggested going back to regular x86 Gentoo in this case is |
28 |
> that it's quite apparent there's a lot of friction in that computer/human |
29 |
> interface at present, and for him, x86 may just work best, at the moment. |
30 |
> While it makes us geek types cringe at the supposed resource waste, is he |
31 |
> actually wasting more /not/ using AMD64 because he's too frustrated with |
32 |
> it, or smoothly using x86, which he knows and is comfortable with? There's |
33 |
> nothing "wrong" wth using it in x86 mode, and if that's what suits is |
34 |
> style best, then more power to him (literally, more power over the |
35 |
> computer)! |
36 |
> |
37 |
> The thing is, it's his decision, not your or mine. He's the one living |
38 |
> with the consequences. If he's more comfortable on x86, and all amd64 is |
39 |
> giving him is frustration, then x86 is the way he should go. If he |
40 |
> believes he can pull it out with the help of a chroot or the like, then |
41 |
> let him try, but don't force it on him, and don't make him so despairing |
42 |
> he quits Gentoo in frustration, when he's already said he's very |
43 |
> comfortable with x86 Gentoo. |
44 |
|
45 |
You're totally correct. I've installed x86 on quite a few AMD64 machines for |
46 |
friends that aren't extremely savvy. Gentoo neophytes shouldn't have to deal |
47 |
with the headaches AMD64 sometimes brings. If the users are high-performance |
48 |
computing types well... I wasn't attempting to pressure him into using AMD64. |
49 |
Only to further elucidate the situation. Hoping that further education on the |
50 |
issue would aid in making decisions. |
51 |
|
52 |
Brandon |