SPEC_CPU_NOZMODIFIER can be used if your compiler does not implement
the C99 standard printf length modifier "z". You'll know you need
this flag if validation fails with the file SPECtestformatmodifier_z.txt

SPEC_CPU_NOZMODIFIER can be used if your compiler does not implement
the C99 standard printf length modifier "z". You'll know you need
this flag if validation fails with the file SPECtestformatmodifier_z.txt

To override one of the options set by /fast, specify that option after the
-fast option on the command line. The exception is the xP or QxP option
which can't be overridden. The options set by /fast may change from
release to release.

F<n>
<n> is the stack reserve amount in bytes. It can be specified as a decimal integer
or by using a C-style convention for constants (for example, -F0x1000).
Default: The stack size default is chosen by the operating system.

To override one of the options set by /fast, specify that option after the
-fast option on the command line. The exception is the xP or QxP option
which can't be overridden. The options set by /fast may change from
release to release.

F<n>
<n> is the stack reserve amount in bytes. It can be specified as a decimal integer
or by using a C-style convention for constants (for example, -F0x1000).
Default: The stack size default is chosen by the operating system.

To override one of the options set by /fast, specify that option after the
-fast option on the command line. The exception is the xP or QxP option
which can't be overridden. The options set by /fast may change from
release to release.

F<n>
<n> is the stack reserve amount in bytes. It can be specified as a decimal integer
or by using a C-style convention for constants (for example, -F0x1000).
Default: The stack size default is chosen by the operating system.

To override one of the options set by /fast, specify that option after the
-fast option on the command line. The exception is the xP or QxP option
which can't be overridden. The options set by /fast may change from
release to release.

F<n>
<n> is the stack reserve amount in bytes. It can be specified as a decimal integer
or by using a C-style convention for constants (for example, -F0x1000).
Default: The stack size default is chosen by the operating system.

Peak Optimization Flags

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.

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, -Qprof_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

To override one of the options set by /fast, specify that option after the
-fast option on the command line. The exception is the xP or QxP option
which can't be overridden. The options set by /fast may change from
release to release.

F<n>
<n> is the stack reserve amount in bytes. It can be specified as a decimal integer
or by using a C-style convention for constants (for example, -F0x1000).
Default: The stack size default is chosen by the operating system.

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.

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, -Qprof_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

To override one of the options set by /fast, specify that option after the
-fast option on the command line. The exception is the xP or QxP option
which can't be overridden. The options set by /fast may change from
release to release.

F<n>
<n> is the stack reserve amount in bytes. It can be specified as a decimal integer
or by using a C-style convention for constants (for example, -F0x1000).
Default: The stack size default is chosen by the operating system.

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.

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, -Qprof_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

To override one of the options set by /fast, specify that option after the
-fast option on the command line. The exception is the xP or QxP option
which can't be overridden. The options set by /fast may change from
release to release.

F<n>
<n> is the stack reserve amount in bytes. It can be specified as a decimal integer
or by using a C-style convention for constants (for example, -F0x1000).
Default: The stack size default is chosen by the operating system.

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.

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, -Qprof_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

To override one of the options set by /fast, specify that option after the
-fast option on the command line. The exception is the xP or QxP option
which can't be overridden. The options set by /fast may change from
release to release.

F<n>
<n> is the stack reserve amount in bytes. It can be specified as a decimal integer
or by using a C-style convention for constants (for example, -F0x1000).
Default: The stack size default is chosen by the operating system.

Implicitly Included Flags

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:
- Loop unrolling, including instruction scheduling
- Code replication to eliminate branches
- Padding the size of certain power-of-two arrays to allow
more efficient cache use.
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. On IA-32
Windows platforms, -O3 sets the following:

Enables optimizations for speed and disables some optimizations that
increase code size and affect speed.
To limit code size, this option:
- Enables global optimization; this includes data-flow analysis,
code motion, strength reduction and test replacement, split-lifetime
analysis, and instruction scheduling.
- Disables intrinsic recognition and intrinsics inlining.
The O1 option may improve performance for applications with very large
code size, many branches, and execution time not dominated by code within loops.
On IA-32 Windows platforms, -O1 sets the following:

Code is optimized for Intel Core Duo processors, Intel Core Solo
processors, Intel Pentium 4 processors with Streaming SIMD Extensions 3,
and compatible Intel processors with Streaming SIMD Extensions 3. 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.

This option improves precision of floating-point divides. It has a slight
impact on speed.

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, use this option to disable the floating-point
division-to-multiplication optimization. The result is more accurate, with some
loss of performance.

If you specify -no-prec-div (Linux and Mac OS) or /Qprec-div- (Windows), it enables
optimizations that give slightly less precise results than full IEEE
division.