CPU2006 Result Flag Description

Base Portability Flags

410.bwaves

- -DSPEC_CPU_LP64
- PORTABILITY
- 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.

416.gamess

- -DSPEC_CPU_LP64
- PORTABILITY
- 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.

433.milc

- -DSPEC_CPU_LP64
- PORTABILITY
- 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.

434.zeusmp

- -DSPEC_CPU_LP64
- PORTABILITY
- 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.

435.gromacs

- -DSPEC_CPU_LP64
- PORTABILITY
- 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.
- -nofor_main
- LDPORTABILITY
- This option specifies that the main program is not written in Fortran. It is a link-time option that prevents the compiler from linking for_main.o into applications.
  
  For example, if the main program is written in C and calls a Fortran subprogram, specify -nofor-main when compiling the program with the ifort command. If you omit this option, the main program must be a Fortran program.

436.cactusADM

- -DSPEC_CPU_LP64
- PORTABILITY
- 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.
- -nofor_main
- LDPORTABILITY
- This option specifies that the main program is not written in Fortran. It is a link-time option that prevents the compiler from linking for_main.o into applications.
  
  For example, if the main program is written in C and calls a Fortran subprogram, specify -nofor-main when compiling the program with the ifort command. If you omit this option, the main program must be a Fortran program.

437.leslie3d

- -DSPEC_CPU_LP64
- PORTABILITY
- 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.

444.namd

- -DSPEC_CPU_LP64
- PORTABILITY
- 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.

447.dealII

- -DSPEC_CPU_LP64
- PORTABILITY
- 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.

450.soplex

- -DSPEC_CPU_LP64
- PORTABILITY
- 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.

453.povray

- -DSPEC_CPU_LP64
- PORTABILITY
- 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.

454.calculix

- -DSPEC_CPU_LP64
- PORTABILITY
- 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.
- -nofor_main
- LDPORTABILITY
- This option specifies that the main program is not written in Fortran. It is a link-time option that prevents the compiler from linking for_main.o into applications.
  
  For example, if the main program is written in C and calls a Fortran subprogram, specify -nofor-main when compiling the program with the ifort command. If you omit this option, the main program must be a Fortran program.

459.GemsFDTD

- -DSPEC_CPU_LP64
- PORTABILITY
- 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.

465.tonto

- -DSPEC_CPU_LP64
- PORTABILITY
- 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.

470.lbm

- -DSPEC_CPU_LP64
- PORTABILITY
- 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.

481.wrf

- -DSPEC_CPU_LP64
- PORTABILITY
- 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.
- -DSPEC_CPU_CASE_FLAG
- CPORTABILITY
- This macro indicates that Fortran functions called from C should have their names lower-cased.
- -DSPEC_CPU_LINUX
- CPORTABILITY
- This macro indicates that the benchmark is being compiled on a Linux system.

482.sphinx3

- -DSPEC_CPU_LP64
- PORTABILITY
- 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.

Base Optimization Flags

C benchmarks

- -xSSE4.2
- COPTIMIZE, OPTIMIZE
- Code is optimized for Intel(R) processors with support for SSE 4.2 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.
- -O3
- COPTIMIZE, OPTIMIZE
- 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.
- Includes:
  - -O2
    - -O1
      
      -funroll-loops
      
      -fno-builtin
      
      -mno-ieee-fp
      
      -fomit-framepointer
      
      -ffunction-sections
      
      -ftz
- -ipo
- COPTIMIZE, OPTIMIZE
- 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
- -no-prec-div
- COPTIMIZE, OPTIMIZE
- (disable/enable[default] -prec-div)
  -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.
- -static
- COPTIMIZE, OPTIMIZE
- Compiler option to statically link in libraries at link time
- -ansi-alias
- COPTIMIZE
- Enable/disable(DEFAULT) use of ANSI aliasing rules in optimizations; user asserts that the program adheres to these rules.

C++ benchmarks

- -xSSE4.2
- CXXOPTIMIZE, OPTIMIZE
- Code is optimized for Intel(R) processors with support for SSE 4.2 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.
- -O3
- CXXOPTIMIZE, OPTIMIZE
- 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.
- Includes:
  - -O2
    - -O1
      
      -funroll-loops
      
      -fno-builtin
      
      -mno-ieee-fp
      
      -fomit-framepointer
      
      -ffunction-sections
      
      -ftz
- -ipo
- CXXOPTIMIZE, OPTIMIZE
- 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
- -no-prec-div
- CXXOPTIMIZE, OPTIMIZE
- (disable/enable[default] -prec-div)
  -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.
- -static
- CXXOPTIMIZE, OPTIMIZE
- Compiler option to statically link in libraries at link time
- -ansi-alias
- CXXOPTIMIZE
- Enable/disable(DEFAULT) use of ANSI aliasing rules in optimizations; user asserts that the program adheres to these rules.

Fortran benchmarks

- -xSSE4.2
- OPTIMIZE
- Code is optimized for Intel(R) processors with support for SSE 4.2 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.
- -O3
- OPTIMIZE
- 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.
- Includes:
  - -O2
    - -O1
      
      -funroll-loops
      
      -fno-builtin
      
      -mno-ieee-fp
      
      -fomit-framepointer
      
      -ffunction-sections
      
      -ftz
- -ipo
- OPTIMIZE
- 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
- -no-prec-div
- OPTIMIZE
- (disable/enable[default] -prec-div)
  -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.
- -static
- OPTIMIZE
- Compiler option to statically link in libraries at link time

Benchmarks using both Fortran and C

- -xSSE4.2
- COPTIMIZE, OPTIMIZE
- Code is optimized for Intel(R) processors with support for SSE 4.2 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.
- -O3
- COPTIMIZE, OPTIMIZE
- 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.
- Includes:
  - -O2
    - -O1
      
      -funroll-loops
      
      -fno-builtin
      
      -mno-ieee-fp
      
      -fomit-framepointer
      
      -ffunction-sections
      
      -ftz
- -ipo
- COPTIMIZE, OPTIMIZE
- 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
- -no-prec-div
- COPTIMIZE, OPTIMIZE
- (disable/enable[default] -prec-div)
  -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.
- -static
- COPTIMIZE, OPTIMIZE
- Compiler option to statically link in libraries at link time
- -ansi-alias
- COPTIMIZE
- Enable/disable(DEFAULT) use of ANSI aliasing rules in optimizations; user asserts that the program adheres to these rules.

Implicitly Included Flags

This section contains descriptions of flags that were included implicitly by other flags, but which do not have a permanent home at SPEC.

For questions about the meanings of these flags, please contact the tester.
For other inquiries, please contact webmaster@spec.org
Copyright 2006-2014 Standard Performance Evaluation Corporation
Tested with SPEC CPU2006 v1.2.
Report generated on Thu Jul 24 03:34:37 2014 by SPEC CPU2006 flags formatter v6906.

CPU2006 Flag Description
ScaleMP vSMP Foundation (Intel Xeon X5650, 2.67 GHz)

Test sponsored by ScaleMP / Cyfronet

Base Compiler Invocation

C benchmarks

C++ benchmarks

Fortran benchmarks

Benchmarks using both Fortran and C

Base Portability Flags

410.bwaves

416.gamess

433.milc

434.zeusmp

435.gromacs

436.cactusADM

437.leslie3d

444.namd

447.dealII

450.soplex

453.povray

454.calculix

459.GemsFDTD

465.tonto

470.lbm

481.wrf

482.sphinx3

Base Optimization Flags

C benchmarks

C++ benchmarks

Fortran benchmarks

Benchmarks using both Fortran and C

Implicitly Included Flags

	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.

CPU2006 Flag DescriptionScaleMP vSMP Foundation (Intel Xeon X5650, 2.67 GHz)

Test sponsored by ScaleMP / Cyfronet

Base Compiler Invocation

Base Portability Flags

Base Optimization Flags

Implicitly Included Flags

CPU2006 Flag Description
ScaleMP vSMP Foundation (Intel Xeon X5650, 2.67 GHz)