1 |
On Tue, Jun 29, 2010 at 8:09 PM, Beau Henderson <beau@××××××××××××.com> wrote: |
2 |
> On 06/30/10 08:07, Paul Hartman wrote: |
3 |
>> |
4 |
>> 2010/6/29 Hasan SAHIN<hasan.sahin@×××.com>: |
5 |
>>> |
6 |
>>> Hello all, |
7 |
>>> |
8 |
>>> I am using Athlon64 X2 processor with the |
9 |
>>> CFLAGS="-march=k8 -O2 -pipe -fomit-frame-pointer" option. |
10 |
>>> |
11 |
>>> Can I use the -march=native option instead of that? |
12 |
>> |
13 |
>> You can see which options -march=native would use by running this command: |
14 |
>> |
15 |
>> gcc -Q --help=target -march=native |
16 |
>> |
17 |
>> (thanks to Daniel Iliev for the tip) |
18 |
>> |
19 |
> |
20 |
> Perhaps I'm missing something but running the above gives me the impression |
21 |
> that -march=native actually only configures the bare minimal install. I'm |
22 |
> not seeing -mmmx or -msse3 enabled on my k8-sse3 for instance ( amongst much |
23 |
> else ). |
24 |
|
25 |
What -march setting is it showing in that output? The MMX (etc) may be |
26 |
enabled implicitly instead of explicitly. |
27 |
|
28 |
It's also possible that the CPU detection is failing to identify your |
29 |
CPU. In that case you could probably file a bug report about it. |