| 1 |
On Wed, Jul 27, 2011 at 5:09 PM, Andy Wilkinson <drukargin@×××××.com> wrote: |
| 2 |
|
| 3 |
> ** |
| 4 |
> On 07/26/2011 12:22 PM, pk wrote: |
| 5 |
> |
| 6 |
> On 2011-07-26 22:36, Alokat wrote: |
| 7 |
> |
| 8 |
> |
| 9 |
> model name : Intel(R) Core(TM)2 Duo CPU L7100 @ 1.20GHz |
| 10 |
> |
| 11 |
> <snip> |
| 12 |
> |
| 13 |
> |
| 14 |
> I guess *core2* is the right one? |
| 15 |
> |
| 16 |
> Yes, acc. to:http://en.gentoo-wiki.com/wiki/Safe_Cflags/Intel#Core_2_Duo.2FQuad.2C_Xeon_51xx.2F53xx.2F54xx.2F3360.2C_Pentium_Dual-Core_T23xx.2B.2FExxxx.2C_Celeron_Dual-Core |
| 17 |
> |
| 18 |
> HTH |
| 19 |
> |
| 20 |
> Best regards |
| 21 |
> |
| 22 |
> Peter K |
| 23 |
> |
| 24 |
> |
| 25 |
> Another good trick I've found on the forums is to run: |
| 26 |
> |
| 27 |
> $ gcc -### -e -v -march=native /usr/include/stdlib.h |
| 28 |
> |
| 29 |
> The last line of output will include the various CFLAGS that -march=native |
| 30 |
> picks. In my case (Phenom II 955): |
| 31 |
> |
| 32 |
> "/usr/libexec/gcc/x86_64-pc-linux-gnu/4.4.5/cc1" "-quiet" |
| 33 |
> "/usr/include/stdlib.h" "-D_FORTIFY_SOURCE=2" *"-march=amdfam10" "-mcx16" |
| 34 |
> "-msahf" "-mpopcnt"* "--param" "l1-cache-size=64" "--param" |
| 35 |
> "l1-cache-line-size=64" "--param" "l2-cache-size=512" "-mtune=amdfam10" |
| 36 |
> "-quiet" "-dumpbase" "stdlib.h" "-auxbase" "stdlib" "-o" "/tmp/ccR1PlNZ.s" |
| 37 |
> "--output-pch=/usr/include/stdlib.h.gch" |
| 38 |
> |
| 39 |
> I typically use -march=native when I don't need to worry about distcc, or |
| 40 |
> the options from that output that start with "-m". |
| 41 |
> |
| 42 |
> -Andy |
| 43 |
> |
| 44 |
I must stay, this is brilliant ! |
| 45 |
Thank you very much. |
| 46 |
|
| 47 |
Kfir |
Archives