A newer version of this document is available. Customers should click here to go to the newest version.
mtune, tune
Performs optimizations for specific processors but does not cause extended instruction sets to be used (unlike -march).
Syntax
Linux: |
-mtune=processor |
Windows: |
/tune:processor |
Arguments
processor |
Is the processor for which the compiler should perform optimizations. Possible values are:
|
Default
generic |
Code is generated for the compiler's default behavior. |
Description
This option performs optimizations for specific processors but does not cause extended instruction sets to be used (unlike -march).
The resulting executable is backwards compatible and generated code is optimized for specific processors. For example, code generated with -mtune=core2 or /tune:core2 runs correctly on 4th Generation Intel® Core™ processors, but it might not run as fast as if it had been generated using -mtune=haswell or /tune:haswell.
Code generated with -mtune=haswell (/tune:haswell) or -mtune=core-avx2 (/tune:core-avx2) will also run correctly on Intel® Core™2 processors, but it might not run as fast as if it had been generated using -mtune=core2 or /tune:core2.
This is in contrast to code generated with -march=core-avx2, which will not run correctly on older processors such as Intel® Core™2 processors.
This option only applies to host compilation. When offloading is enabled, it does not impact device-specific compilation.
Product and Performance Information |
---|
Performance varies by use, configuration and other factors. Learn more at www.Intel.com/PerformanceIndex. Notice revision #20201201 |
IDE Equivalent
Visual Studio: Code Generation >Intel Processor Microarchitecture-Specific Optimization
Alternate Options
None