| 1 |
> 2008/11/26 Sebastian Klüsener <sebastian@×××××.de>: |
| 2 |
>> I'd change that to 'march=amdfam10' or 'march=native' if your gcc is a |
| 3 |
>> recent one. Recent means >=4.3. |
| 4 |
>> |
| 5 |
> please don't top post. |
| 6 |
> second, what does march=native does?! |
| 7 |
> |
| 8 |
> -- |
| 9 |
> dott. ing. beso |
| 10 |
|
| 11 |
Hi Beso. |
| 12 |
|
| 13 |
http://gcc.gnu.org/onlinedocs/gcc-4.3.2/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options |
| 14 |
|
| 15 |
"native |
| 16 |
This selects the CPU to tune for at compilation time by determining the |
| 17 |
processor type of the compiling machine. Using -mtune=native will produce |
| 18 |
code optimized for the local machine under the constraints of the selected |
| 19 |
instruction set. Using -march=native will enable all instruction subsets |
| 20 |
supported by the local machine (hence the result might not run on different |
| 21 |
machines). " |
| 22 |
|
| 23 |
Best Regards, |
| 24 |
Eduardo. |
Archives