1 |
Andrew Gaydenko wrote: |
2 |
> I have noticed, the official portage tree has included gcc 4.2. Now for |
3 |
> Core 2 Duo CPU (amd64 Gentoo arch) I use in make.conf file: |
4 |
> |
5 |
> CFLAGS="-O2 -march=nocona -pipe" |
6 |
> |
7 |
> gcc' changelog has this note: |
8 |
> |
9 |
> -------------------- |
10 |
> ... |
11 |
> IA-32/x86-64 |
12 |
> |
13 |
> * -mtune=generic can now be used to generate code running well on common x86 chips. |
14 |
> This includes AMD Athlon, AMD Opteron, Intel Pentium-M, Intel Pentium 4 and Intel |
15 |
> Core 2. |
16 |
> * -mtune=native and -march=native will produce code optimized for the host |
17 |
> architecture as detected using the cpuid instruction. |
18 |
> ... |
19 |
> -------------------- |
20 |
> |
21 |
> The question is: must I replace '-march=nocona' with '-mtune=native and -march=native'? |
22 |
|
23 |
I have a Core2 Duo E6600 and use these CFLAGS with GCC 4.2: |
24 |
|
25 |
CFLAGS="-Os -march=native -mtune=native -fomit-frame-pointer -pipe -mmmx |
26 |
-msse2 -msse3" |
27 |
|
28 |
Native works fine here. |
29 |
-- |
30 |
Kenneth Prugh - Ken69267 |
31 |
Gentoo AMD64 Arch Tester |