1 |
On Wed, Jul 27, 2011 at 5:34 PM, Kfir Lavi <lavi.kfir@×××××.com> wrote: |
2 |
|
3 |
> |
4 |
> |
5 |
> On Wed, Jul 27, 2011 at 5:09 PM, Andy Wilkinson <drukargin@×××××.com>wrote: |
6 |
> |
7 |
>> ** |
8 |
>> On 07/26/2011 12:22 PM, pk wrote: |
9 |
>> |
10 |
>> On 2011-07-26 22:36, Alokat wrote: |
11 |
>> |
12 |
>> |
13 |
>> model name : Intel(R) Core(TM)2 Duo CPU L7100 @ 1.20GHz |
14 |
>> |
15 |
>> <snip> |
16 |
>> |
17 |
>> |
18 |
>> I guess *core2* is the right one? |
19 |
>> |
20 |
>> 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 |
21 |
>> |
22 |
>> HTH |
23 |
>> |
24 |
>> Best regards |
25 |
>> |
26 |
>> Peter K |
27 |
>> |
28 |
>> |
29 |
>> Another good trick I've found on the forums is to run: |
30 |
>> |
31 |
>> $ gcc -### -e -v -march=native /usr/include/stdlib.h |
32 |
>> |
33 |
>> The last line of output will include the various CFLAGS that -march=native |
34 |
>> picks. In my case (Phenom II 955): |
35 |
>> |
36 |
>> "/usr/libexec/gcc/x86_64-pc-linux-gnu/4.4.5/cc1" "-quiet" |
37 |
>> "/usr/include/stdlib.h" "-D_FORTIFY_SOURCE=2" *"-march=amdfam10" "-mcx16" |
38 |
>> "-msahf" "-mpopcnt"* "--param" "l1-cache-size=64" "--param" |
39 |
>> "l1-cache-line-size=64" "--param" "l2-cache-size=512" "-mtune=amdfam10" |
40 |
>> "-quiet" "-dumpbase" "stdlib.h" "-auxbase" "stdlib" "-o" "/tmp/ccR1PlNZ.s" |
41 |
>> "--output-pch=/usr/include/stdlib.h.gch" |
42 |
>> |
43 |
>> I typically use -march=native when I don't need to worry about distcc, or |
44 |
>> the options from that output that start with "-m". |
45 |
>> |
46 |
>> -Andy |
47 |
>> |
48 |
> I must stay, this is brilliant ! |
49 |
> Thank you very much. |
50 |
> |
51 |
> Kfir |
52 |
> |
53 |
|
54 |
Just shared this trick in my blog. |
55 |
http://gentoo-what-did-you-say.blogspot.com/2011/07/finding-cpu-flags-using-gcc.html |
56 |
I added a link to this thread in the post. |
57 |
|
58 |
Kfir |