Copyright © 2016 Intel Corporation. All Rights Reserved.
![[user]](http://www.spec.org/auto/cpu2006/flags/user.png)
Invoke the Intel C compiler 17.0 for IA32 applications when the environment is set for Intel 64 compilation.
Invoke the Intel C++ compiler 17.0 for IA32 applications when the environment is set for Intel 64 compilation.
Invoke the Intel C compiler 17.0 for IA32 applications when the environment is set for Intel 64 compilation.
Invoke the Intel C compiler 17.0 for Intel 64 applications
Invoke the Intel C compiler 17.0 for Intel 64 applications
Invoke the Intel C compiler 17.0 for Intel 64 applications
Invoke the Intel C compiler 17.0 for Intel 64 applications
Invoke the Intel C++ compiler 17.0 for IA32 applications when the environment is set for Intel 64 compilation.
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
![[benchmark]](http://www.spec.org/auto/cpu2006/flags/benchmark.png)
This macro indicates that the benchmark is being compiled on an Intel IA32-compatible system running the Linux operating system.
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
Portability changes for Linux
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
This flag can be set for SPEC compilation for Linux using default compiler.
This macro specifies that the target system uses the LP64 data model; specifically, that integers are 32 bits, while longs and pointers are 64 bits.
This macro indicates that the benchmark is being compiled on an AMD64-compatible system running the Linux operating system.
![[suite]](http://www.spec.org/auto/cpu2006/flags/suite.png)
This option is used to indicate that the host system's integers are 32-bits wide, and longs and pointers are 64-bits wide. Not all benchmarks recognize this macro, but the preferred practice for data model selection applies the flags to all benchmarks; this flag description is a placeholder for those benchmarks that do not recognize this macro.
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
This option is used to indicate that the host system's integers are 32-bits wide, and longs and pointers are 64-bits wide. Not all benchmarks recognize this macro, but the preferred practice for data model selection applies the flags to all benchmarks; this flag description is a placeholder for those benchmarks that do not recognize this macro.
This option is used to indicate that the host system's integers are 32-bits wide, and longs and pointers are 64-bits wide. Not all benchmarks recognize this macro, but the preferred practice for data model selection applies the flags to all benchmarks; this flag description is a placeholder for those benchmarks that do not recognize this macro.
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
Portability changes for Linux
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
This macro determines which file system interface will be used. Common file i/o calls like stat() and readdir() return off_t data that may or may not fit within a 32bit data structure if this flag is not used. With _FILE_OFFSET_BITS=64, types like off_t have a size of 64 bits. The truncation that happens without _FILE_OFFSET_BITS=64 has been observed to yield intermittent failures.
Ex: RHEL7 distributions format partitions using xfs. Runtime errors are observed on such systems because sometimes returned values will not fit into 32bit data types that are a mismatch for xfs.
See the gnuc feature test macros article for more information.
This flag can be set for SPEC compilation for Linux using default compiler.
Code is optimized for Intel(R) processors with support for AVX2 instructions. The resulting code may contain unconditional use of features that are not supported on other processors. This option also enables new optimizations in addition to Intel processor-specific optimizations including advanced data layout and code restructuring optimizations to improve memory accesses for Intel processors.
Do not use this option if you are executing a program on a processor that is not an Intel processor. If you use this option on a non-compatible processor to compile the main program (in Fortran) or the function main() in C/C++, the program will display a fatal run-time error if they are executed on unsupported processors.
Multi-file ip optimizations that includes:
- inline function expansion
- interprocedural constant propogation
- dead code elimination
- propagation of function characteristics
- passing arguments in registers
- loop-invariant code motion
Enables O2 optimizations plus more aggressive optimizations, such as prefetching, scalar replacement, and loop and memory access transformations. Enables optimizations for maximum speed, such as:
On IA-32 and Intel EM64T processors, when O3 is used with options -ax or -x (Linux) or with options /Qax or /Qx (Windows), the compiler performs more aggressive data dependency analysis than for O2, which may result in longer compilation times. The O3 optimizations may not cause higher performance unless loop and memory access transformations take place. The optimizations may slow down code in some cases compared to O2 optimizations. The O3 option is recommended for applications that have loops that heavily use floating-point calculations and process large data sets.
-no-prec-div enables optimizations that give slightly less precise results than full IEEE division.
When you specify -no-prec-div along with some optimizations, such as -xN and -xB (Linux) or /QxN and /QxB (Windows), the compiler may change floating-point division computations into multiplication by the reciprocal of the denominator. For example, A/B is computed as A * (1/B) to improve the speed of the computation.
However, sometimes the value produced by this transformation is not as accurate as full IEEE division. When it is important to have fully precise IEEE division, do not use -no-prec-div. This will enable the default -prec-div and the result will be more accurate, with some loss of performance.
Enable/disable(DEFAULT) the compiler to generate prefetch instructions to prefetch data.
Controls the level of memory layout transformations performed by the compiler. This option can improve cache reuse and cache locality.
Code is optimized for Intel(R) processors with support for AVX2 instructions. The resulting code may contain unconditional use of features that are not supported on other processors. This option also enables new optimizations in addition to Intel processor-specific optimizations including advanced data layout and code restructuring optimizations to improve memory accesses for Intel processors.
Do not use this option if you are executing a program on a processor that is not an Intel processor. If you use this option on a non-compatible processor to compile the main program (in Fortran) or the function main() in C/C++, the program will display a fatal run-time error if they are executed on unsupported processors.
Multi-file ip optimizations that includes:
- inline function expansion
- interprocedural constant propogation
- dead code elimination
- propagation of function characteristics
- passing arguments in registers
- loop-invariant code motion
Enables O2 optimizations plus more aggressive optimizations, such as prefetching, scalar replacement, and loop and memory access transformations. Enables optimizations for maximum speed, such as:
On IA-32 and Intel EM64T processors, when O3 is used with options -ax or -x (Linux) or with options /Qax or /Qx (Windows), the compiler performs more aggressive data dependency analysis than for O2, which may result in longer compilation times. The O3 optimizations may not cause higher performance unless loop and memory access transformations take place. The optimizations may slow down code in some cases compared to O2 optimizations. The O3 option is recommended for applications that have loops that heavily use floating-point calculations and process large data sets.
-no-prec-div enables optimizations that give slightly less precise results than full IEEE division.
When you specify -no-prec-div along with some optimizations, such as -xN and -xB (Linux) or /QxN and /QxB (Windows), the compiler may change floating-point division computations into multiplication by the reciprocal of the denominator. For example, A/B is computed as A * (1/B) to improve the speed of the computation.
However, sometimes the value produced by this transformation is not as accurate as full IEEE division. When it is important to have fully precise IEEE division, do not use -no-prec-div. This will enable the default -prec-div and the result will be more accurate, with some loss of performance.
Enable/disable(DEFAULT) the compiler to generate prefetch instructions to prefetch data.
Controls the level of memory layout transformations performed by the compiler. This option can improve cache reuse and cache locality.
Enable SmartHeap and/or other library usage by forcing the linker to ignore multiple definitions if present
MicroQuill SmartHeap Library (32-bit) available from http://www.microquill.com/
Instrument program for profiling for the first phase of two-phase profile guided otimization. This instrumentation gathers information about a program's execution paths and data values but does not gather information from hardware performance counters. The profile instrumentation also gathers data for optimizations which are unique to profile-feedback optimization.
-profgen:threadsafe option collects profile guidaed optimization data with guards for threaded applications.
Instructs the compiler to produce a profile-optimized
executable and merges available dynamic information (.dyn)
files into a pgopti.dpi file. If you perform multiple
executions of the instrumented program, -prof-use merges
the dynamic information files again and overwrites the
previous pgopti.dpi file.
Without any other options, the current directory is
searched for .dyn files
Code is optimized for Intel(R) processors with support for AVX2 instructions. The resulting code may contain unconditional use of features that are not supported on other processors. This option also enables new optimizations in addition to Intel processor-specific optimizations including advanced data layout and code restructuring optimizations to improve memory accesses for Intel processors.
Do not use this option if you are executing a program on a processor that is not an Intel processor. If you use this option on a non-compatible processor to compile the main program (in Fortran) or the function main() in C/C++, the program will display a fatal run-time error if they are executed on unsupported processors.
Allows for tuning of application performance by setting the number of threads to use in a parallel region. It has a similar effect as environment variable OMP_NUM_THREADS. This option overrides the environment variable when both are specified. Ex: -par-num-threads=1 specifies one thread to use.
Multi-file ip optimizations that includes:
- inline function expansion
- interprocedural constant propogation
- dead code elimination
- propagation of function characteristics
- passing arguments in registers
- loop-invariant code motion
Enables O2 optimizations plus more aggressive optimizations, such as prefetching, scalar replacement, and loop and memory access transformations. Enables optimizations for maximum speed, such as:
On IA-32 and Intel EM64T processors, when O3 is used with options -ax or -x (Linux) or with options /Qax or /Qx (Windows), the compiler performs more aggressive data dependency analysis than for O2, which may result in longer compilation times. The O3 optimizations may not cause higher performance unless loop and memory access transformations take place. The optimizations may slow down code in some cases compared to O2 optimizations. The O3 option is recommended for applications that have loops that heavily use floating-point calculations and process large data sets.
-no-prec-div enables optimizations that give slightly less precise results than full IEEE division.
When you specify -no-prec-div along with some optimizations, such as -xN and -xB (Linux) or /QxN and /QxB (Windows), the compiler may change floating-point division computations into multiplication by the reciprocal of the denominator. For example, A/B is computed as A * (1/B) to improve the speed of the computation.
However, sometimes the value produced by this transformation is not as accurate as full IEEE division. When it is important to have fully precise IEEE division, do not use -no-prec-div. This will enable the default -prec-div and the result will be more accurate, with some loss of performance.
This option instructs the compiler to analyze and transform the program so that 64-bit pointers are shrunk to 32-bit pointers, and 64-bit longs (on Linux) are shrunk into 32-bit longs wherever it is legal and safe to do so. In order for this option to be effective the compiler must be able to optimize using the -ipo/-Qipo option and must be able to analyze all library/external calls the program makes.
This option requires that the size of the program executable never exceeds 2^32 bytes and all data values can be represented within 32 bits. If the program can run correctly in a 32-bit system, these requirements are implicitly satisfied. If the program violates these size restrictions, unpredictable behavior might occur.
Controls the level of memory layout transformations performed by the compiler. This option can improve cache reuse and cache locality.
Instrument program for profiling for the first phase of two-phase profile guided otimization. This instrumentation gathers information about a program's execution paths and data values but does not gather information from hardware performance counters. The profile instrumentation also gathers data for optimizations which are unique to profile-feedback optimization.
-profgen:threadsafe option collects profile guidaed optimization data with guards for threaded applications.
Instructs the compiler to produce a profile-optimized
executable and merges available dynamic information (.dyn)
files into a pgopti.dpi file. If you perform multiple
executions of the instrumented program, -prof-use merges
the dynamic information files again and overwrites the
previous pgopti.dpi file.
Without any other options, the current directory is
searched for .dyn files
Code is optimized for Intel(R) processors with support for AVX2 instructions. The resulting code may contain unconditional use of features that are not supported on other processors. This option also enables new optimizations in addition to Intel processor-specific optimizations including advanced data layout and code restructuring optimizations to improve memory accesses for Intel processors.
Do not use this option if you are executing a program on a processor that is not an Intel processor. If you use this option on a non-compatible processor to compile the main program (in Fortran) or the function main() in C/C++, the program will display a fatal run-time error if they are executed on unsupported processors.
Allows for tuning of application performance by setting the number of threads to use in a parallel region. It has a similar effect as environment variable OMP_NUM_THREADS. This option overrides the environment variable when both are specified. Ex: -par-num-threads=1 specifies one thread to use.
Multi-file ip optimizations that includes:
- inline function expansion
- interprocedural constant propogation
- dead code elimination
- propagation of function characteristics
- passing arguments in registers
- loop-invariant code motion
Enables O2 optimizations plus more aggressive optimizations, such as prefetching, scalar replacement, and loop and memory access transformations. Enables optimizations for maximum speed, such as:
On IA-32 and Intel EM64T processors, when O3 is used with options -ax or -x (Linux) or with options /Qax or /Qx (Windows), the compiler performs more aggressive data dependency analysis than for O2, which may result in longer compilation times. The O3 optimizations may not cause higher performance unless loop and memory access transformations take place. The optimizations may slow down code in some cases compared to O2 optimizations. The O3 option is recommended for applications that have loops that heavily use floating-point calculations and process large data sets.
-no-prec-div enables optimizations that give slightly less precise results than full IEEE division.
When you specify -no-prec-div along with some optimizations, such as -xN and -xB (Linux) or /QxN and /QxB (Windows), the compiler may change floating-point division computations into multiplication by the reciprocal of the denominator. For example, A/B is computed as A * (1/B) to improve the speed of the computation.
However, sometimes the value produced by this transformation is not as accurate as full IEEE division. When it is important to have fully precise IEEE division, do not use -no-prec-div. This will enable the default -prec-div and the result will be more accurate, with some loss of performance.
Enable/disable(DEFAULT) the compiler to generate prefetch instructions to prefetch data.
This option instructs the compiler to analyze and transform the program so that 64-bit pointers are shrunk to 32-bit pointers, and 64-bit longs (on Linux) are shrunk into 32-bit longs wherever it is legal and safe to do so. In order for this option to be effective the compiler must be able to optimize using the -ipo/-Qipo option and must be able to analyze all library/external calls the program makes.
This option requires that the size of the program executable never exceeds 2^32 bytes and all data values can be represented within 32 bits. If the program can run correctly in a 32-bit system, these requirements are implicitly satisfied. If the program violates these size restrictions, unpredictable behavior might occur.
Controls the level of memory layout transformations performed by the compiler. This option can improve cache reuse and cache locality.
Code is optimized for Intel(R) processors with support for AVX2 instructions. The resulting code may contain unconditional use of features that are not supported on other processors. This option also enables new optimizations in addition to Intel processor-specific optimizations including advanced data layout and code restructuring optimizations to improve memory accesses for Intel processors.
Do not use this option if you are executing a program on a processor that is not an Intel processor. If you use this option on a non-compatible processor to compile the main program (in Fortran) or the function main() in C/C++, the program will display a fatal run-time error if they are executed on unsupported processors.
Multi-file ip optimizations that includes:
- inline function expansion
- interprocedural constant propogation
- dead code elimination
- propagation of function characteristics
- passing arguments in registers
- loop-invariant code motion
Enables O2 optimizations plus more aggressive optimizations, such as prefetching, scalar replacement, and loop and memory access transformations. Enables optimizations for maximum speed, such as:
On IA-32 and Intel EM64T processors, when O3 is used with options -ax or -x (Linux) or with options /Qax or /Qx (Windows), the compiler performs more aggressive data dependency analysis than for O2, which may result in longer compilation times. The O3 optimizations may not cause higher performance unless loop and memory access transformations take place. The optimizations may slow down code in some cases compared to O2 optimizations. The O3 option is recommended for applications that have loops that heavily use floating-point calculations and process large data sets.
-no-prec-div enables optimizations that give slightly less precise results than full IEEE division.
When you specify -no-prec-div along with some optimizations, such as -xN and -xB (Linux) or /QxN and /QxB (Windows), the compiler may change floating-point division computations into multiplication by the reciprocal of the denominator. For example, A/B is computed as A * (1/B) to improve the speed of the computation.
However, sometimes the value produced by this transformation is not as accurate as full IEEE division. When it is important to have fully precise IEEE division, do not use -no-prec-div. This will enable the default -prec-div and the result will be more accurate, with some loss of performance.
Controls the level of memory layout transformations performed by the compiler. This option can improve cache reuse and cache locality.
Instrument program for profiling for the first phase of two-phase profile guided otimization. This instrumentation gathers information about a program's execution paths and data values but does not gather information from hardware performance counters. The profile instrumentation also gathers data for optimizations which are unique to profile-feedback optimization.
-profgen:threadsafe option collects profile guidaed optimization data with guards for threaded applications.
Instructs the compiler to produce a profile-optimized
executable and merges available dynamic information (.dyn)
files into a pgopti.dpi file. If you perform multiple
executions of the instrumented program, -prof-use merges
the dynamic information files again and overwrites the
previous pgopti.dpi file.
Without any other options, the current directory is
searched for .dyn files
Code is optimized for Intel(R) processors with support for AVX2 instructions. The resulting code may contain unconditional use of features that are not supported on other processors. This option also enables new optimizations in addition to Intel processor-specific optimizations including advanced data layout and code restructuring optimizations to improve memory accesses for Intel processors.
Do not use this option if you are executing a program on a processor that is not an Intel processor. If you use this option on a non-compatible processor to compile the main program (in Fortran) or the function main() in C/C++, the program will display a fatal run-time error if they are executed on unsupported processors.
Allows for tuning of application performance by setting the number of threads to use in a parallel region. It has a similar effect as environment variable OMP_NUM_THREADS. This option overrides the environment variable when both are specified. Ex: -par-num-threads=1 specifies one thread to use.
Multi-file ip optimizations that includes:
- inline function expansion
- interprocedural constant propogation
- dead code elimination
- propagation of function characteristics
- passing arguments in registers
- loop-invariant code motion
Enables O2 optimizations plus more aggressive optimizations, such as prefetching, scalar replacement, and loop and memory access transformations. Enables optimizations for maximum speed, such as:
On IA-32 and Intel EM64T processors, when O3 is used with options -ax or -x (Linux) or with options /Qax or /Qx (Windows), the compiler performs more aggressive data dependency analysis than for O2, which may result in longer compilation times. The O3 optimizations may not cause higher performance unless loop and memory access transformations take place. The optimizations may slow down code in some cases compared to O2 optimizations. The O3 option is recommended for applications that have loops that heavily use floating-point calculations and process large data sets.
-no-prec-div enables optimizations that give slightly less precise results than full IEEE division.
When you specify -no-prec-div along with some optimizations, such as -xN and -xB (Linux) or /QxN and /QxB (Windows), the compiler may change floating-point division computations into multiplication by the reciprocal of the denominator. For example, A/B is computed as A * (1/B) to improve the speed of the computation.
However, sometimes the value produced by this transformation is not as accurate as full IEEE division. When it is important to have fully precise IEEE division, do not use -no-prec-div. This will enable the default -prec-div and the result will be more accurate, with some loss of performance.
Controls the level of memory layout transformations performed by the compiler. This option can improve cache reuse and cache locality.
Code is optimized for Intel(R) processors with support for AVX2 instructions. The resulting code may contain unconditional use of features that are not supported on other processors. This option also enables new optimizations in addition to Intel processor-specific optimizations including advanced data layout and code restructuring optimizations to improve memory accesses for Intel processors.
Do not use this option if you are executing a program on a processor that is not an Intel processor. If you use this option on a non-compatible processor to compile the main program (in Fortran) or the function main() in C/C++, the program will display a fatal run-time error if they are executed on unsupported processors.
Multi-file ip optimizations that includes:
- inline function expansion
- interprocedural constant propogation
- dead code elimination
- propagation of function characteristics
- passing arguments in registers
- loop-invariant code motion
Enables O2 optimizations plus more aggressive optimizations, such as prefetching, scalar replacement, and loop and memory access transformations. Enables optimizations for maximum speed, such as:
On IA-32 and Intel EM64T processors, when O3 is used with options -ax or -x (Linux) or with options /Qax or /Qx (Windows), the compiler performs more aggressive data dependency analysis than for O2, which may result in longer compilation times. The O3 optimizations may not cause higher performance unless loop and memory access transformations take place. The optimizations may slow down code in some cases compared to O2 optimizations. The O3 option is recommended for applications that have loops that heavily use floating-point calculations and process large data sets.
-no-prec-div enables optimizations that give slightly less precise results than full IEEE division.
When you specify -no-prec-div along with some optimizations, such as -xN and -xB (Linux) or /QxN and /QxB (Windows), the compiler may change floating-point division computations into multiplication by the reciprocal of the denominator. For example, A/B is computed as A * (1/B) to improve the speed of the computation.
However, sometimes the value produced by this transformation is not as accurate as full IEEE division. When it is important to have fully precise IEEE division, do not use -no-prec-div. This will enable the default -prec-div and the result will be more accurate, with some loss of performance.
This option sets the maximum number of times a loop can be unrolled, to 2.
This option instructs the compiler to analyze and transform the program so that 64-bit pointers are shrunk to 32-bit pointers, and 64-bit longs (on Linux) are shrunk into 32-bit longs wherever it is legal and safe to do so. In order for this option to be effective the compiler must be able to optimize using the -ipo/-Qipo option and must be able to analyze all library/external calls the program makes.
This option requires that the size of the program executable never exceeds 2^32 bytes and all data values can be represented within 32 bits. If the program can run correctly in a 32-bit system, these requirements are implicitly satisfied. If the program violates these size restrictions, unpredictable behavior might occur.
Controls the level of memory layout transformations performed by the compiler. This option can improve cache reuse and cache locality.
Instrument program for profiling for the first phase of two-phase profile guided otimization. This instrumentation gathers information about a program's execution paths and data values but does not gather information from hardware performance counters. The profile instrumentation also gathers data for optimizations which are unique to profile-feedback optimization.
-profgen:threadsafe option collects profile guidaed optimization data with guards for threaded applications.
Instructs the compiler to produce a profile-optimized
executable and merges available dynamic information (.dyn)
files into a pgopti.dpi file. If you perform multiple
executions of the instrumented program, -prof-use merges
the dynamic information files again and overwrites the
previous pgopti.dpi file.
Without any other options, the current directory is
searched for .dyn files
Code is optimized for Intel(R) processors with support for AVX2 instructions. The resulting code may contain unconditional use of features that are not supported on other processors. This option also enables new optimizations in addition to Intel processor-specific optimizations including advanced data layout and code restructuring optimizations to improve memory accesses for Intel processors.
Do not use this option if you are executing a program on a processor that is not an Intel processor. If you use this option on a non-compatible processor to compile the main program (in Fortran) or the function main() in C/C++, the program will display a fatal run-time error if they are executed on unsupported processors.
Allows for tuning of application performance by setting the number of threads to use in a parallel region. It has a similar effect as environment variable OMP_NUM_THREADS. This option overrides the environment variable when both are specified. Ex: -par-num-threads=1 specifies one thread to use.
Multi-file ip optimizations that includes:
- inline function expansion
- interprocedural constant propogation
- dead code elimination
- propagation of function characteristics
- passing arguments in registers
- loop-invariant code motion
Enables O2 optimizations plus more aggressive optimizations, such as prefetching, scalar replacement, and loop and memory access transformations. Enables optimizations for maximum speed, such as:
On IA-32 and Intel EM64T processors, when O3 is used with options -ax or -x (Linux) or with options /Qax or /Qx (Windows), the compiler performs more aggressive data dependency analysis than for O2, which may result in longer compilation times. The O3 optimizations may not cause higher performance unless loop and memory access transformations take place. The optimizations may slow down code in some cases compared to O2 optimizations. The O3 option is recommended for applications that have loops that heavily use floating-point calculations and process large data sets.
-no-prec-div enables optimizations that give slightly less precise results than full IEEE division.
When you specify -no-prec-div along with some optimizations, such as -xN and -xB (Linux) or /QxN and /QxB (Windows), the compiler may change floating-point division computations into multiplication by the reciprocal of the denominator. For example, A/B is computed as A * (1/B) to improve the speed of the computation.
However, sometimes the value produced by this transformation is not as accurate as full IEEE division. When it is important to have fully precise IEEE division, do not use -no-prec-div. This will enable the default -prec-div and the result will be more accurate, with some loss of performance.
This option sets the maximum number of times a loop can be unrolled, to 4.
This option instructs the compiler to analyze and transform the program so that 64-bit pointers are shrunk to 32-bit pointers, and 64-bit longs (on Linux) are shrunk into 32-bit longs wherever it is legal and safe to do so. In order for this option to be effective the compiler must be able to optimize using the -ipo/-Qipo option and must be able to analyze all library/external calls the program makes.
This option requires that the size of the program executable never exceeds 2^32 bytes and all data values can be represented within 32 bits. If the program can run correctly in a 32-bit system, these requirements are implicitly satisfied. If the program violates these size restrictions, unpredictable behavior might occur.
Controls the level of memory layout transformations performed by the compiler. This option can improve cache reuse and cache locality.
Instrument program for profiling for the first phase of two-phase profile guided otimization. This instrumentation gathers information about a program's execution paths and data values but does not gather information from hardware performance counters. The profile instrumentation also gathers data for optimizations which are unique to profile-feedback optimization.
-profgen:threadsafe option collects profile guidaed optimization data with guards for threaded applications.
Instructs the compiler to produce a profile-optimized
executable and merges available dynamic information (.dyn)
files into a pgopti.dpi file. If you perform multiple
executions of the instrumented program, -prof-use merges
the dynamic information files again and overwrites the
previous pgopti.dpi file.
Without any other options, the current directory is
searched for .dyn files
Code is optimized for Intel(R) processors with support for AVX2 instructions. The resulting code may contain unconditional use of features that are not supported on other processors. This option also enables new optimizations in addition to Intel processor-specific optimizations including advanced data layout and code restructuring optimizations to improve memory accesses for Intel processors.
Do not use this option if you are executing a program on a processor that is not an Intel processor. If you use this option on a non-compatible processor to compile the main program (in Fortran) or the function main() in C/C++, the program will display a fatal run-time error if they are executed on unsupported processors.
Allows for tuning of application performance by setting the number of threads to use in a parallel region. It has a similar effect as environment variable OMP_NUM_THREADS. This option overrides the environment variable when both are specified. Ex: -par-num-threads=1 specifies one thread to use.
Multi-file ip optimizations that includes:
- inline function expansion
- interprocedural constant propogation
- dead code elimination
- propagation of function characteristics
- passing arguments in registers
- loop-invariant code motion
Enables O2 optimizations plus more aggressive optimizations, such as prefetching, scalar replacement, and loop and memory access transformations. Enables optimizations for maximum speed, such as:
On IA-32 and Intel EM64T processors, when O3 is used with options -ax or -x (Linux) or with options /Qax or /Qx (Windows), the compiler performs more aggressive data dependency analysis than for O2, which may result in longer compilation times. The O3 optimizations may not cause higher performance unless loop and memory access transformations take place. The optimizations may slow down code in some cases compared to O2 optimizations. The O3 option is recommended for applications that have loops that heavily use floating-point calculations and process large data sets.
-no-prec-div enables optimizations that give slightly less precise results than full IEEE division.
When you specify -no-prec-div along with some optimizations, such as -xN and -xB (Linux) or /QxN and /QxB (Windows), the compiler may change floating-point division computations into multiplication by the reciprocal of the denominator. For example, A/B is computed as A * (1/B) to improve the speed of the computation.
However, sometimes the value produced by this transformation is not as accurate as full IEEE division. When it is important to have fully precise IEEE division, do not use -no-prec-div. This will enable the default -prec-div and the result will be more accurate, with some loss of performance.
This option sets the maximum number of times a loop can be unrolled, to 2.
Controls the level of memory layout transformations performed by the compiler. This option can improve cache reuse and cache locality.
Instrument program for profiling for the first phase of two-phase profile guided otimization. This instrumentation gathers information about a program's execution paths and data values but does not gather information from hardware performance counters. The profile instrumentation also gathers data for optimizations which are unique to profile-feedback optimization.
-profgen:threadsafe option collects profile guidaed optimization data with guards for threaded applications.
Instructs the compiler to produce a profile-optimized
executable and merges available dynamic information (.dyn)
files into a pgopti.dpi file. If you perform multiple
executions of the instrumented program, -prof-use merges
the dynamic information files again and overwrites the
previous pgopti.dpi file.
Without any other options, the current directory is
searched for .dyn files
Code is optimized for Intel(R) processors with support for AVX2 instructions. The resulting code may contain unconditional use of features that are not supported on other processors. This option also enables new optimizations in addition to Intel processor-specific optimizations including advanced data layout and code restructuring optimizations to improve memory accesses for Intel processors.
Do not use this option if you are executing a program on a processor that is not an Intel processor. If you use this option on a non-compatible processor to compile the main program (in Fortran) or the function main() in C/C++, the program will display a fatal run-time error if they are executed on unsupported processors.
Allows for tuning of application performance by setting the number of threads to use in a parallel region. It has a similar effect as environment variable OMP_NUM_THREADS. This option overrides the environment variable when both are specified. Ex: -par-num-threads=1 specifies one thread to use.
Multi-file ip optimizations that includes:
- inline function expansion
- interprocedural constant propogation
- dead code elimination
- propagation of function characteristics
- passing arguments in registers
- loop-invariant code motion
Enables O2 optimizations plus more aggressive optimizations, such as prefetching, scalar replacement, and loop and memory access transformations. Enables optimizations for maximum speed, such as:
On IA-32 and Intel EM64T processors, when O3 is used with options -ax or -x (Linux) or with options /Qax or /Qx (Windows), the compiler performs more aggressive data dependency analysis than for O2, which may result in longer compilation times. The O3 optimizations may not cause higher performance unless loop and memory access transformations take place. The optimizations may slow down code in some cases compared to O2 optimizations. The O3 option is recommended for applications that have loops that heavily use floating-point calculations and process large data sets.
-no-prec-div enables optimizations that give slightly less precise results than full IEEE division.
When you specify -no-prec-div along with some optimizations, such as -xN and -xB (Linux) or /QxN and /QxB (Windows), the compiler may change floating-point division computations into multiplication by the reciprocal of the denominator. For example, A/B is computed as A * (1/B) to improve the speed of the computation.
However, sometimes the value produced by this transformation is not as accurate as full IEEE division. When it is important to have fully precise IEEE division, do not use -no-prec-div. This will enable the default -prec-div and the result will be more accurate, with some loss of performance.
Select the method that the register allocator uses to partition each routine into regions
Controls the level of memory layout transformations performed by the compiler. This option can improve cache reuse and cache locality.
Enable SmartHeap and/or other library usage by forcing the linker to ignore multiple definitions if present
MicroQuill SmartHeap Library (32-bit) available from http://www.microquill.com/
This allows alloca to be set to the compiler's preferred alloca by SPEC rules.
This allows alloca to be set to the compiler's preferred alloca by SPEC rules.
This section contains descriptions of flags that were included implicitly by other flags, but which do not have a permanent home at SPEC.
Enables optimizations for speed. This is the generally recommended
optimization level. This option also enables:
- Inlining of intrinsics
- Intra-file interprocedural optimizations, which include:
- inlining
- constant propagation
- forward substitution
- routine attribute propagation
- variable address-taken analysis
- dead static function elimination
- removal of unreferenced variables
- The following capabilities for performance gain:
- constant propagation
- copy propagation
- dead-code elimination
- global register allocation
- global instruction scheduling and control speculation
- loop unrolling
- optimized code selection
- partial redundancy elimination
- strength reduction/induction variable simplification
- variable renaming
- exception handling optimizations
- tail recursions
- peephole optimizations
- structure assignment lowering and optimizations
- dead store elimination
Enables optimizations for speed and disables some optimizations that increase code size and affect speed.
To limit code size, this option:
The O1 option may improve performance for applications with very large code size, many branches, and execution time not dominated by code within loops.
-O1 sets the following options:Tells the compiler the maximum number of times to unroll loops. For example -funroll-loops0 would disable unrolling of loops.
-fno-builtin disables inline expansion for all intrinsic functions.
This option trades off floating-point precision for speed by removing the restriction to conform to the IEEE standard.
EBP is used as a general-purpose register in optimizations.
Places each function in its own COMDAT section.
Flushes denormal results to zero.
This BIOS option allows you to determine whether system Performance or energy efficiency is more important on server. This can be one of the following: Balanced Energy, Balanced Performance, Energy Efficient and Performance.
This BIOS option allows to configure memory reliability, availability and serviceability (RAS). Setting this BIOS option to Performance, system performance is optimized Setting this BIOS option to RAS mode, lockstep technology is enabled and serviceability is improved.
This BIOS option allows to configure the periodicity of memory scrubbing. Setting this BIOS option to Disable, no systematic periodic scrubbing is done Setting this BIOS option to an integer from 1 to 24 ensures all the memory is scanned in that number of hours
Enabling this option allows the processor cores to automatically increase its frequency and increasing performance if it is running below power, temperature.
Sets the stack size to n kbytes, or unlimited to allow the stack size to grow without limit.
Launching a process with numactl --interleave=all sets the memory interleave policy so that memory will be allocated using round robin on nodes. When memory cannot be allocated on the current interleave target fall back to other nodes.
The Baseboard Management Controller allows the consfiguration of functional profiles. The default functional profile is modified to set the Full Fan Speed option.
mpol=[default|prefer:Node|bind:NodeList|interleave|interleave:NodeList] Set the NUMA memory allocation policy for all files in that instance (if the kernel CONFIG_NUMA is enabled) - which can be adjusted on the fly via 'mount -o remount ...'
default
prefers to allocate memory from the local node
prefer:Node
prefers to allocate memory from the given Node
bind:NodeList
allocates memory only from nodes in NodeList
interleave
prefers to allocate from each node in turn
interleave:NodeList
allocates from each node of NodeList in turn.
The NodeList format is a comma-separated list of decimal numbers and ranges, a range being two hyphen-separated decimal numbers, the smallest and largest node numbers in the range. For example, mpol=bind:0-3,5,7,9-15 Note that trying to mount a tmpfs with an mpol option will fail if the running kernel does not support NUMA; and will fail if its nodelist specifies a node which is not online. If your system relies on that tmpfs being mounted, but from time to time runs a kernel built without NUMA capability (perhaps a safe recovery kernel), or with fewer nodes online, then it is advisable to omit the mpol option from automatic mount options. It can be added later, when the tmpfs is already mounted on MountPoint, by 'mount -o remount,mpol=Policy:NodeList MountPoint'.
The directory containing all spec files, including temporary and binary files, is mapped to memory.
This directory is created using linux command mount -t tmpfs -o size=1536g,rw,mpol=interleave none /specRam
then all spec files are copied into it before starting the test.
One TB is allocated evenly distributed on all the numa nodes.
Flag description origin markings:
|
Indicates that the flag description came from the user flags file. |
|
Indicates that the flag description came from the suite-wide flags file. |
|
Indicates that the flag description came from a per-benchmark flags file. |
For questions about the meanings of these flags, please contact the tester.
For other inquiries, please contact webmaster@spec.org
Copyright 2006-2017 Standard Performance Evaluation Corporation
Tested with SPEC CPU2006 v1.2.
Report generated on Tue May 2 14:04:53 2017 by SPEC CPU2006 flags formatter v6906.