| 1 |
On Wed, Sep 20, 2006 at 04:25:12PM -0400, Jack Lloyd wrote: |
| 2 |
> |
| 3 |
> Tomorrow my new Core 2 workstation should be arriving, and reading |
| 4 |
> through the 2006.1 amd64 install notes and so forth, the recomended |
| 5 |
> CFLAGS for EM64T CPUs is -march=nocona. However as that is tuned for |
| 6 |
> 64-bit enabled Netburst rather than Conroe, I'm wondering if anyone |
| 7 |
> had thoughts on good flags. In particular as (to the extent that I |
| 8 |
> know anything about microarchitecture), Conroe seems closer to a K8 |
| 9 |
> than a P4, especially with regards to pipeline length and execution |
| 10 |
> resources, I'm not sure that P4/Netburst tuning is the right thing to |
| 11 |
> do. But the GCC docs say that -march=k8 enables 3dnow, which Intel |
| 12 |
> chips don't have. So, right now the "seems likely" options would |
| 13 |
> be: |
| 14 |
> |
| 15 |
> -march=k8 -mno-3dnow -msse3 |
| 16 |
> -march=nocona |
| 17 |
> -march=pentium-m -m64 [saw this suggested in the forums, seems like a bad idea] |
| 18 |
> |
| 19 |
|
| 20 |
I've got a Dell XPS 700 with an E6600, and, like you, wondered what were |
| 21 |
the "best" CFLAGS to choose. Lacking any solid directions, I went with: |
| 22 |
|
| 23 |
CFLAGS="-march=nocona -O2 -pipe" |
| 24 |
CHOST="x86_64-pc-linux-gnu" |
| 25 |
CXXFLAGS="${CFLAGS}" |
| 26 |
MAKEOPTS="-j3" |
| 27 |
|
| 28 |
Simple, and nothing fancy. |
| 29 |
|
| 30 |
I'm happy to say that my 2006.1 amd64 install seems to be working great. |
| 31 |
I'm running unstable, btw, which I've been doing on my old athlon64 for |
| 32 |
a couple years now. |
| 33 |
|
| 34 |
I'm still tweaking my kernel options though. |
| 35 |
|
| 36 |
P.S. It's amazing how fast a kernel builds and emerges happen on the new |
| 37 |
Core 2. |
| 38 |
|
| 39 |
-- |
| 40 |
Eric Augustus |
| 41 |
shrike@×××××××××.com |
| 42 |
----------------- |
| 43 |
Are we on STRIKE yet? |
| 44 |
-- |
| 45 |
gentoo-amd64@g.o mailing list |
Archives