OMP2012 Flag Description
SGI SGI UV 300 (Intel Xeon E7-8867 v4, 2.40 GHz)

Base Optimization Flags

C benchmarks

• • -O3
  • 
  • COPTIMIZE

  • 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
• • -xCORE-AVX2
  • 
  • COPTIMIZE

  • Generates code for processors that support Intel(R) Advanced Vector Extensions 2 (Intel(R) AVX2), Intel(R) AVX, SSE4.2, SSE4.1, SSE3, SSE2, SSE, and SSSE3 instructions.

    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.

• • -ipo1
  • 
  • COPTIMIZE

  • 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

    (n - number of ipo files generated during build)
• • -openmp
  • 
  • COPTIMIZE

  • Enable the compiler to generate multi-threaded code based on the OpenMP* directives.

• • -ansi-alias
  • 
  • COPTIMIZE

  • Enable/disable(DEFAULT) use of ANSI aliasing rules in optimizations; user asserts that the program adheres to these rules.

• • -mcmodel=medium
  • 
  • COPTIMIZE

  • Syntax: -mcmodel=mem_model

    mcmodel is the memory model to use. Possible values are:

    small

    Tells the compiler to restrict code and data to the first 2GB of address space. All accesses of code and data can be done with Instruction Pointer (IP)-relative addressing.

    medium

    Tells the compiler to restrict code to the first 2GB; it places no memory restriction on data. Accesses of code can be done with IP-relative addressing, but accesses of data must be done with absolute addressing.

    large

    Places no memory restriction on code or data. All accesses of code and data must be done with absolute addressing.< /p>

    Default

    -mcmodel=small

    On systems using Intel(R) 64 architecture, the compiler restricts code and data to the first 2GB of address space. Instruction Pointer (IP)-relative addressing can be used to access code and data.

• • -shared-intel
  • 
  • COPTIMIZE

  • This option causes Intel-provided libraries to be linked in dynamically.

C++ benchmarks

• • -O3
  • 
  • CXXOPTIMIZE

  • 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
• • -xCORE-AVX2
  • 
  • CXXOPTIMIZE

  • Generates code for processors that support Intel(R) Advanced Vector Extensions 2 (Intel(R) AVX2), Intel(R) AVX, SSE4.2, SSE4.1, SSE3, SSE2, SSE, and SSSE3 instructions.

    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.

• • -ipo1
  • 
  • CXXOPTIMIZE

  • 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

    (n - number of ipo files generated during build)
• • -openmp
  • 
  • CXXOPTIMIZE

  • Enable the compiler to generate multi-threaded code based on the OpenMP* directives.

• • -ansi-alias
  • 
  • CXXOPTIMIZE

  • Enable/disable(DEFAULT) use of ANSI aliasing rules in optimizations; user asserts that the program adheres to these rules.

• • -mcmodel=medium
  • 
  • CXXOPTIMIZE

  • Syntax: -mcmodel=mem_model

    mcmodel is the memory model to use. Possible values are:

    small

    Tells the compiler to restrict code and data to the first 2GB of address space. All accesses of code and data can be done with Instruction Pointer (IP)-relative addressing.

    medium

    Tells the compiler to restrict code to the first 2GB; it places no memory restriction on data. Accesses of code can be done with IP-relative addressing, but accesses of data must be done with absolute addressing.

    large

    Places no memory restriction on code or data. All accesses of code and data must be done with absolute addressing.< /p>

    Default

    -mcmodel=small

    On systems using Intel(R) 64 architecture, the compiler restricts code and data to the first 2GB of address space. Instruction Pointer (IP)-relative addressing can be used to access code and data.

• • -shared-intel
  • 
  • CXXOPTIMIZE

  • This option causes Intel-provided libraries to be linked in dynamically.

Fortran benchmarks

• • -O3
  • 
  • FOPTIMIZE

  • 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
• • -xCORE-AVX2
  • 
  • FOPTIMIZE

  • Generates code for processors that support Intel(R) Advanced Vector Extensions 2 (Intel(R) AVX2), Intel(R) AVX, SSE4.2, SSE4.1, SSE3, SSE2, SSE, and SSSE3 instructions.

    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.

• • -ipo1
  • 
  • FOPTIMIZE

  • 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

    (n - number of ipo files generated during build)
• • -openmp
  • 
  • FOPTIMIZE

  • Enable the compiler to generate multi-threaded code based on the OpenMP* directives.

• • -mcmodel=medium
  • 
  • FOPTIMIZE

  • Syntax: -mcmodel=mem_model

    mcmodel is the memory model to use. Possible values are:

    small

    Tells the compiler to restrict code and data to the first 2GB of address space. All accesses of code and data can be done with Instruction Pointer (IP)-relative addressing.

    medium

    Tells the compiler to restrict code to the first 2GB; it places no memory restriction on data. Accesses of code can be done with IP-relative addressing, but accesses of data must be done with absolute addressing.

    large

    Places no memory restriction on code or data. All accesses of code and data must be done with absolute addressing.< /p>

    Default

    -mcmodel=small

    On systems using Intel(R) 64 architecture, the compiler restricts code and data to the first 2GB of address space. Instruction Pointer (IP)-relative addressing can be used to access code and data.

• • -shared-intel
  • 
  • FOPTIMIZE

  • This option causes Intel-provided libraries to be linked in dynamically.

• • -align array64byte
  • 
  • FOPTIMIZE

  • specify how data items are aligned
    keywords: all (same as -align), none (same as -noalign),
    [no]commons, [no]dcommons,
    [no]qcommons, [no]zcommons,
    rec1byte, rec2byte, rec4byte,
    rec8byte, rec16byte, rec32byte,
    array8byte, array16byte, array32byte,
    array64byte, array128byte, array256byte,
    [no]records, [no]sequence
    

Peak Optimization Flags

C benchmarks

352.nab

• • -O3
  • 
  • COPTIMIZE

  • 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
• • -xCORE-AVX2
  • 
  • COPTIMIZE

  • Generates code for processors that support Intel(R) Advanced Vector Extensions 2 (Intel(R) AVX2), Intel(R) AVX, SSE4.2, SSE4.1, SSE3, SSE2, SSE, and SSSE3 instructions.

    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.

• • -ipo1
  • 
  • COPTIMIZE

  • 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

    (n - number of ipo files generated during build)
• • -openmp
  • 
  • COPTIMIZE

  • Enable the compiler to generate multi-threaded code based on the OpenMP* directives.

• • -ansi-alias
  • 
  • COPTIMIZE

  • Enable/disable(DEFAULT) use of ANSI aliasing rules in optimizations; user asserts that the program adheres to these rules.

• • -mcmodel=medium
  • 
  • COPTIMIZE

  • Syntax: -mcmodel=mem_model

    mcmodel is the memory model to use. Possible values are:

    small

    Tells the compiler to restrict code and data to the first 2GB of address space. All accesses of code and data can be done with Instruction Pointer (IP)-relative addressing.

    medium

    Tells the compiler to restrict code to the first 2GB; it places no memory restriction on data. Accesses of code can be done with IP-relative addressing, but accesses of data must be done with absolute addressing.

    large

    Places no memory restriction on code or data. All accesses of code and data must be done with absolute addressing.< /p>

    Default

    -mcmodel=small

    On systems using Intel(R) 64 architecture, the compiler restricts code and data to the first 2GB of address space. Instruction Pointer (IP)-relative addressing can be used to access code and data.

• • -shared-intel
  • 
  • COPTIMIZE

  • This option causes Intel-provided libraries to be linked in dynamically.

358.botsalgn

• • Same as 352.nab

359.botsspar

• • basepeak = yes

367.imagick

• • Same as 352.nab

372.smithwa

• • Same as 352.nab

C++ benchmarks

• • -O3
  • 
  • CXXOPTIMIZE

  • 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
• • -xCORE-AVX2
  • 
  • CXXOPTIMIZE

  • Generates code for processors that support Intel(R) Advanced Vector Extensions 2 (Intel(R) AVX2), Intel(R) AVX, SSE4.2, SSE4.1, SSE3, SSE2, SSE, and SSSE3 instructions.

    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.

• • -ipo1
  • 
  • CXXOPTIMIZE

  • 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

    (n - number of ipo files generated during build)
• • -openmp
  • 
  • CXXOPTIMIZE

  • Enable the compiler to generate multi-threaded code based on the OpenMP* directives.

• • -ansi-alias
  • 
  • CXXOPTIMIZE

  • Enable/disable(DEFAULT) use of ANSI aliasing rules in optimizations; user asserts that the program adheres to these rules.

• • -mcmodel=medium
  • 
  • CXXOPTIMIZE

  • Syntax: -mcmodel=mem_model

    mcmodel is the memory model to use. Possible values are:

    small

    Tells the compiler to restrict code and data to the first 2GB of address space. All accesses of code and data can be done with Instruction Pointer (IP)-relative addressing.

    medium

    Tells the compiler to restrict code to the first 2GB; it places no memory restriction on data. Accesses of code can be done with IP-relative addressing, but accesses of data must be done with absolute addressing.

    large

    Places no memory restriction on code or data. All accesses of code and data must be done with absolute addressing.< /p>

    Default

    -mcmodel=small

    On systems using Intel(R) 64 architecture, the compiler restricts code and data to the first 2GB of address space. Instruction Pointer (IP)-relative addressing can be used to access code and data.

• • -shared-intel
  • 
  • CXXOPTIMIZE

  • This option causes Intel-provided libraries to be linked in dynamically.

Fortran benchmarks

• • -O3
  • 
  • FOPTIMIZE

  • 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
• • -xCORE-AVX2
  • 
  • FOPTIMIZE

  • Generates code for processors that support Intel(R) Advanced Vector Extensions 2 (Intel(R) AVX2), Intel(R) AVX, SSE4.2, SSE4.1, SSE3, SSE2, SSE, and SSSE3 instructions.

    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.

• • -ipo1
  • 
  • FOPTIMIZE

  • 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

    (n - number of ipo files generated during build)
• • -openmp
  • 
  • FOPTIMIZE

  • Enable the compiler to generate multi-threaded code based on the OpenMP* directives.

• • -mcmodel=medium
  • 
  • FOPTIMIZE

  • Syntax: -mcmodel=mem_model

    mcmodel is the memory model to use. Possible values are:

    small

    Tells the compiler to restrict code and data to the first 2GB of address space. All accesses of code and data can be done with Instruction Pointer (IP)-relative addressing.

    medium

    Tells the compiler to restrict code to the first 2GB; it places no memory restriction on data. Accesses of code can be done with IP-relative addressing, but accesses of data must be done with absolute addressing.

    large

    Places no memory restriction on code or data. All accesses of code and data must be done with absolute addressing.< /p>

    Default

    -mcmodel=small

    On systems using Intel(R) 64 architecture, the compiler restricts code and data to the first 2GB of address space. Instruction Pointer (IP)-relative addressing can be used to access code and data.

• • -shared-intel
  • 
  • FOPTIMIZE

  • This option causes Intel-provided libraries to be linked in dynamically.

• • -align array64byte
  • 
  • FOPTIMIZE

  • specify how data items are aligned
    keywords: all (same as -align), none (same as -noalign),
    [no]commons, [no]dcommons,
    [no]qcommons, [no]zcommons,
    rec1byte, rec2byte, rec4byte,
    rec8byte, rec16byte, rec32byte,
    array8byte, array16byte, array32byte,
    array64byte, array128byte, array256byte,
    [no]records, [no]sequence