1 |
On 10/04/2010 23:06, luis jure wrote: |
2 |
> |
3 |
> hello list, |
4 |
> |
5 |
> after many years without a hardware upgrade, i'll be receiving my new |
6 |
> computer next week: intel i7 920 cpu, 6 GB ram, asus p6t mobo. |
7 |
> |
8 |
> i'm pretty excited, i imagine that at first i'll be shocked at the |
9 |
> difference with the ancient machine i'm using now. |
10 |
> |
11 |
> now my question: searching a bit for the best compilation flags for |
12 |
> this processor, i found this at gentoo-wiki: |
13 |
> |
14 |
> CHOST="x86_64-pc-linux-gnu" |
15 |
> CFLAGS="-march=core2 -msse4 -mcx16 -msahf -O2 -pipe" |
16 |
> CXXFLAGS="${CFLAGS}" |
17 |
> (http://en.gentoo-wiki.com/wiki/Safe_Cflags/Intel) |
18 |
> |
19 |
> on the other hand, a thread at http://forums.gentoo.org says that the |
20 |
> wiki page is outdated, and that -march=native should do the job without |
21 |
> any further tweaks like -msse4 etc. |
22 |
|
23 |
That is correct; -march=native will indeed do the job. The CFLAGS |
24 |
example you cite is clearly an interpretation of the flags that the |
25 |
native target would result in anyway. |
26 |
|
27 |
With respect to my Intel Xeon E3113, -march=native appears to equate to: |
28 |
|
29 |
-march=core2 -mtune=core2 -msahf -msse4.1 --param l1-cache-size=32 |
30 |
--param l1-cache-line-size=64 |
31 |
|
32 |
In short, use "native" and let the compiler take care of the details. |
33 |
|
34 |
Cheers, |
35 |
|
36 |
--Kerin |