CPU2006 Result Flag Description

This flags disclosure file describes the compiler flags associated with the following Intel compilers:

Base Compiler Invocation

C benchmarks

- icc
- CC, LD
- icc invokes the Intel C++ compiler. It is invoked as:
  
  icc [ options ] file1 [ file2 ... ]
  
  where,
  - options: represent zero or more compile options
  - fileN: is a C/C++ source (.C .c .cc .cp .cpp .cxx .c++ .i), assembly (.s), object (.o), static library (.a), or other linkable file.
  Invoking the compiler using icc compiles .c and .i files as C. Using icc only links in C++ libraries if C++ source is provided on the command line.

C++ benchmarks

- icpc
- CXXC, LD
- The icpc command uses the same compiler options as the icc command. Invoking the compiler using icpc compiles .c, and .i files as C++. Using icpc always links in C++ libraries.

Fortran benchmarks

- ifort
- FC, LD
- ifort invokes the Intel Fortran compiler. It is invoked as:
  
  ifort [ options ] file1 [ file2 ... ]
  
  where,
  - options: represent zero or more compile options
  - fileN: is a Fortran source file, assembly file, object file, object library, or other linkable file.

Benchmarks using both Fortran and C

- icc
- CC
- icc invokes the Intel C++ compiler. It is invoked as:
  
  icc [ options ] file1 [ file2 ... ]
  
  where,
  - options: represent zero or more compile options
  - fileN: is a C/C++ source (.C .c .cc .cp .cpp .cxx .c++ .i), assembly (.s), object (.o), static library (.a), or other linkable file.
  Invoking the compiler using icc compiles .c and .i files as C. Using icc only links in C++ libraries if C++ source is provided on the command line.
- ifort
- FC, LD
- ifort invokes the Intel Fortran compiler. It is invoked as:
  
  ifort [ options ] file1 [ file2 ... ]
  
  where,
  - options: represent zero or more compile options
  - fileN: is a Fortran source file, assembly file, object file, object library, or other linkable file.

Peak Compiler Invocation

C benchmarks

- icc
- CC, LD
- icc invokes the Intel C++ compiler. It is invoked as:
  
  icc [ options ] file1 [ file2 ... ]
  
  where,
  - options: represent zero or more compile options
  - fileN: is a C/C++ source (.C .c .cc .cp .cpp .cxx .c++ .i), assembly (.s), object (.o), static library (.a), or other linkable file.
  Invoking the compiler using icc compiles .c and .i files as C. Using icc only links in C++ libraries if C++ source is provided on the command line.

C++ benchmarks

- icpc
- CXXC, LD
- The icpc command uses the same compiler options as the icc command. Invoking the compiler using icpc compiles .c, and .i files as C++. Using icpc always links in C++ libraries.

Fortran benchmarks

- ifort
- FC, LD
- ifort invokes the Intel Fortran compiler. It is invoked as:
  
  ifort [ options ] file1 [ file2 ... ]
  
  where,
  - options: represent zero or more compile options
  - fileN: is a Fortran source file, assembly file, object file, object library, or other linkable file.

Benchmarks using both Fortran and C

- icc
- CC
- icc invokes the Intel C++ compiler. It is invoked as:
  
  icc [ options ] file1 [ file2 ... ]
  
  where,
  - options: represent zero or more compile options
  - fileN: is a C/C++ source (.C .c .cc .cp .cpp .cxx .c++ .i), assembly (.s), object (.o), static library (.a), or other linkable file.
  Invoking the compiler using icc compiles .c and .i files as C. Using icc only links in C++ libraries if C++ source is provided on the command line.
- ifort
- FC, LD
- ifort invokes the Intel Fortran compiler. It is invoked as:
  
  ifort [ options ] file1 [ file2 ... ]
  
  where,
  - options: represent zero or more compile options
  - fileN: is a Fortran source file, assembly file, object file, object library, or other linkable file.

Base Portability Flags

435.gromacs

- -nofor_main
- PORTABILITY
- For mixed-language benchmarks, tell the compiler that the main program is not written in Fortran

436.cactusADM

- -nofor_main
- PORTABILITY
- For mixed-language benchmarks, tell the compiler that the main program is not written in Fortran

454.calculix

- -nofor_main
- PORTABILITY
- For mixed-language benchmarks, tell the compiler that the main program is not written in Fortran

481.wrf

- -DSPEC_CPU_MACOSX
- CPORTABILITY
- This macro indicates that the benchmark is being compiled on a MacOS X system.
- -DSPEC_CPU_MACOSX_INTEL
- CPORTABILITY
- This macro indicates that the benchmark is being compiled on an Intel-architecture MacOS X system.
- -DSPEC_CPU_CASE_FLAG
- CPORTABILITY
- This macro indicates that Fortran functions called from C should have their names lower-cased.

Peak Portability Flags

435.gromacs

- -nofor_main
- PORTABILITY
- For mixed-language benchmarks, tell the compiler that the main program is not written in Fortran

436.cactusADM

- -nofor_main
- PORTABILITY
- For mixed-language benchmarks, tell the compiler that the main program is not written in Fortran

454.calculix

- -nofor_main
- PORTABILITY
- For mixed-language benchmarks, tell the compiler that the main program is not written in Fortran

481.wrf

- -DSPEC_CPU_MACOSX
- CPORTABILITY
- This macro indicates that the benchmark is being compiled on a MacOS X system.
- -DSPEC_CPU_MACOSX_INTEL
- CPORTABILITY
- This macro indicates that the benchmark is being compiled on an Intel-architecture MacOS X system.
- -DSPEC_CPU_CASE_FLAG
- CPORTABILITY
- This macro indicates that Fortran functions called from C should have their names lower-cased.

Base Optimization Flags

C benchmarks

- -fast
- COPTIMIZE
- The -fast option enhances execution speed across the entire program by including the following options that can improve run-time performance:
  - -O3 (maximum speed and high-level optimizations)
  - -ipo (enables interprocedural optimizations across files)
  - -no-prec-div (disable -prec-div), where -prec-div improves precision of FP divides (some speed impact)
  - -mdynamic-no-pic, where -mydynamic-no-pic indicates that code is not relocatable
  To override one of the options set by -fast, specify that option after the -fast option on the command line. The options set by -fast may change from release to release.
- Includes:

C++ benchmarks

- -fast
- CXXOPTIMIZE
- The -fast option enhances execution speed across the entire program by including the following options that can improve run-time performance:
  - -O3 (maximum speed and high-level optimizations)
  - -ipo (enables interprocedural optimizations across files)
  - -no-prec-div (disable -prec-div), where -prec-div improves precision of FP divides (some speed impact)
  - -mdynamic-no-pic, where -mydynamic-no-pic indicates that code is not relocatable
  To override one of the options set by -fast, specify that option after the -fast option on the command line. The options set by -fast may change from release to release.
- Includes:

Fortran benchmarks

- -fast
- FOPTIMIZE
- The -fast option enhances execution speed across the entire program by including the following options that can improve run-time performance:
  - -O3 (maximum speed and high-level optimizations)
  - -ipo (enables interprocedural optimizations across files)
  - -no-prec-div (disable -prec-div), where -prec-div improves precision of FP divides (some speed impact)
  - -mdynamic-no-pic, where -mydynamic-no-pic indicates that code is not relocatable
  To override one of the options set by -fast, specify that option after the -fast option on the command line. The options set by -fast may change from release to release.
- Includes:

Benchmarks using both Fortran and C

- -fast
- COPTIMIZE, FOPTIMIZE
- The -fast option enhances execution speed across the entire program by including the following options that can improve run-time performance:
  - -O3 (maximum speed and high-level optimizations)
  - -ipo (enables interprocedural optimizations across files)
  - -no-prec-div (disable -prec-div), where -prec-div improves precision of FP divides (some speed impact)
  - -mdynamic-no-pic, where -mydynamic-no-pic indicates that code is not relocatable
  To override one of the options set by -fast, specify that option after the -fast option on the command line. The options set by -fast may change from release to release.
- Includes:

Base Other Flags

C benchmarks

- -Wl,-stack_addr,0xF0000000
- EXTRA_LDFLAGS
- Specifies the initial address of the stack pointer value, where value is a hexadecimal number rounded to the segment alignment. The default segment alignment is the target pagesize (currently, 1000 hexadecimal for the PowerPC and for i386). If -stack_size is specified and -stack_addr is not, a default stack address specific for the architecture being linked will be used and its value printed as a warning message. This creates a segment named __UNIXSTACK. Note that the initial stack address will be either at the high address of the segment or the low address of the segment depending on which direction the stack grows for the architecture being linked.
- -Wl,-stack_size,0x3F000000
- EXTRA_LDFLAGS
- Specifies the size of the stack segment value, where value is a hexadecimal number rounded to the segment alignment. The default segment alignment is the target pagesize (currently, 1000 hexadecimal for the PowerPC and for i386). If -stack_addr is specified and -stack_size is not, a default stack size specific for the architecture being linked will be used and its value printed as a warning message. This creates a segment named __UNIXSTACK .

C++ benchmarks

- -Wl,-stack_addr,0xF0000000
- EXTRA_LDFLAGS
- Specifies the initial address of the stack pointer value, where value is a hexadecimal number rounded to the segment alignment. The default segment alignment is the target pagesize (currently, 1000 hexadecimal for the PowerPC and for i386). If -stack_size is specified and -stack_addr is not, a default stack address specific for the architecture being linked will be used and its value printed as a warning message. This creates a segment named __UNIXSTACK. Note that the initial stack address will be either at the high address of the segment or the low address of the segment depending on which direction the stack grows for the architecture being linked.
- -Wl,-stack_size,0x3F000000
- EXTRA_LDFLAGS
- Specifies the size of the stack segment value, where value is a hexadecimal number rounded to the segment alignment. The default segment alignment is the target pagesize (currently, 1000 hexadecimal for the PowerPC and for i386). If -stack_addr is specified and -stack_size is not, a default stack size specific for the architecture being linked will be used and its value printed as a warning message. This creates a segment named __UNIXSTACK .

Fortran benchmarks

- -Wl,-stack_addr,0xF0000000
- EXTRA_LDFLAGS
- Specifies the initial address of the stack pointer value, where value is a hexadecimal number rounded to the segment alignment. The default segment alignment is the target pagesize (currently, 1000 hexadecimal for the PowerPC and for i386). If -stack_size is specified and -stack_addr is not, a default stack address specific for the architecture being linked will be used and its value printed as a warning message. This creates a segment named __UNIXSTACK. Note that the initial stack address will be either at the high address of the segment or the low address of the segment depending on which direction the stack grows for the architecture being linked.
- -Wl,-stack_size,0x3F000000
- EXTRA_LDFLAGS
- Specifies the size of the stack segment value, where value is a hexadecimal number rounded to the segment alignment. The default segment alignment is the target pagesize (currently, 1000 hexadecimal for the PowerPC and for i386). If -stack_addr is specified and -stack_size is not, a default stack size specific for the architecture being linked will be used and its value printed as a warning message. This creates a segment named __UNIXSTACK .

Benchmarks using both Fortran and C

- -Wl,-stack_addr,0xF0000000
- EXTRA_LDFLAGS
- Specifies the initial address of the stack pointer value, where value is a hexadecimal number rounded to the segment alignment. The default segment alignment is the target pagesize (currently, 1000 hexadecimal for the PowerPC and for i386). If -stack_size is specified and -stack_addr is not, a default stack address specific for the architecture being linked will be used and its value printed as a warning message. This creates a segment named __UNIXSTACK. Note that the initial stack address will be either at the high address of the segment or the low address of the segment depending on which direction the stack grows for the architecture being linked.
- -Wl,-stack_size,0x3F000000
- EXTRA_LDFLAGS
- Specifies the size of the stack segment value, where value is a hexadecimal number rounded to the segment alignment. The default segment alignment is the target pagesize (currently, 1000 hexadecimal for the PowerPC and for i386). If -stack_addr is specified and -stack_size is not, a default stack size specific for the architecture being linked will be used and its value printed as a warning message. This creates a segment named __UNIXSTACK .

Peak Other Flags

C benchmarks

- -Wl,-stack_addr,0xF0000000
- EXTRA_LDFLAGS
- Specifies the initial address of the stack pointer value, where value is a hexadecimal number rounded to the segment alignment. The default segment alignment is the target pagesize (currently, 1000 hexadecimal for the PowerPC and for i386). If -stack_size is specified and -stack_addr is not, a default stack address specific for the architecture being linked will be used and its value printed as a warning message. This creates a segment named __UNIXSTACK. Note that the initial stack address will be either at the high address of the segment or the low address of the segment depending on which direction the stack grows for the architecture being linked.
- -Wl,-stack_size,0x3F000000
- EXTRA_LDFLAGS
- Specifies the size of the stack segment value, where value is a hexadecimal number rounded to the segment alignment. The default segment alignment is the target pagesize (currently, 1000 hexadecimal for the PowerPC and for i386). If -stack_addr is specified and -stack_size is not, a default stack size specific for the architecture being linked will be used and its value printed as a warning message. This creates a segment named __UNIXSTACK .

C++ benchmarks

- -Wl,-stack_addr,0xF0000000
- EXTRA_LDFLAGS
- Specifies the initial address of the stack pointer value, where value is a hexadecimal number rounded to the segment alignment. The default segment alignment is the target pagesize (currently, 1000 hexadecimal for the PowerPC and for i386). If -stack_size is specified and -stack_addr is not, a default stack address specific for the architecture being linked will be used and its value printed as a warning message. This creates a segment named __UNIXSTACK. Note that the initial stack address will be either at the high address of the segment or the low address of the segment depending on which direction the stack grows for the architecture being linked.
- -Wl,-stack_size,0x3F000000
- EXTRA_LDFLAGS
- Specifies the size of the stack segment value, where value is a hexadecimal number rounded to the segment alignment. The default segment alignment is the target pagesize (currently, 1000 hexadecimal for the PowerPC and for i386). If -stack_addr is specified and -stack_size is not, a default stack size specific for the architecture being linked will be used and its value printed as a warning message. This creates a segment named __UNIXSTACK .

Fortran benchmarks

- -Wl,-stack_addr,0xF0000000
- EXTRA_LDFLAGS
- Specifies the initial address of the stack pointer value, where value is a hexadecimal number rounded to the segment alignment. The default segment alignment is the target pagesize (currently, 1000 hexadecimal for the PowerPC and for i386). If -stack_size is specified and -stack_addr is not, a default stack address specific for the architecture being linked will be used and its value printed as a warning message. This creates a segment named __UNIXSTACK. Note that the initial stack address will be either at the high address of the segment or the low address of the segment depending on which direction the stack grows for the architecture being linked.
- -Wl,-stack_size,0x3F000000
- EXTRA_LDFLAGS
- Specifies the size of the stack segment value, where value is a hexadecimal number rounded to the segment alignment. The default segment alignment is the target pagesize (currently, 1000 hexadecimal for the PowerPC and for i386). If -stack_addr is specified and -stack_size is not, a default stack size specific for the architecture being linked will be used and its value printed as a warning message. This creates a segment named __UNIXSTACK .

Benchmarks using both Fortran and C

- -Wl,-stack_addr,0xF0000000
- EXTRA_LDFLAGS
- Specifies the initial address of the stack pointer value, where value is a hexadecimal number rounded to the segment alignment. The default segment alignment is the target pagesize (currently, 1000 hexadecimal for the PowerPC and for i386). If -stack_size is specified and -stack_addr is not, a default stack address specific for the architecture being linked will be used and its value printed as a warning message. This creates a segment named __UNIXSTACK. Note that the initial stack address will be either at the high address of the segment or the low address of the segment depending on which direction the stack grows for the architecture being linked.
- -Wl,-stack_size,0x3F000000
- EXTRA_LDFLAGS
- Specifies the size of the stack segment value, where value is a hexadecimal number rounded to the segment alignment. The default segment alignment is the target pagesize (currently, 1000 hexadecimal for the PowerPC and for i386). If -stack_addr is specified and -stack_size is not, a default stack size specific for the architecture being linked will be used and its value printed as a warning message. This creates a segment named __UNIXSTACK .

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.

System and Other Tuning Information

The system under test is deemed reasonably quiet by turning off the following from the System Preferences panel:

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 v90.
Report generated on Tue Jul 22 10:01:48 2014 by SPEC CPU2006 flags formatter v6906.

	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 DescriptionApple Computer, Inc. iMac 20-inch 2.0GHz Intel Core Duo

Base Compiler Invocation

Peak Compiler Invocation

Base Portability Flags

Peak Portability Flags

Base Optimization Flags

Peak Optimization Flags

Base Other Flags

Peak Other Flags

Implicitly Included Flags

CPU2006 Flag Description
Apple Computer, Inc. iMac 20-inch 2.0GHz Intel Core Duo