Différences
Ci-dessous, les différences entre deux révisions de la page.
| Les deux révisions précédentes Révision précédente Prochaine révision | Révision précédente | ||
| intel-cluster-studio [2015/02/25 13:27] – [Links] admin | intel-cluster-studio [2015/02/27 13:18] (Version actuelle) – supprimée admin | ||
|---|---|---|---|
| Ligne 1: | Ligne 1: | ||
| - | ====== Intel Cluster Studio XE 2013 ====== | ||
| - | Intel Cluster Studio XE 2013 meets the challenges facing HPC developers by providing, for the first time, a comprehensive suite of tools that enables developers to boost HPC application performance and reliability. It combines Intel’s proven cluster tools with Intel’s advanced threading/ | ||
| - | |||
| - | |||
| - | * Intel® C++ Compiler XE 14.0.2 | ||
| - | * Intel® Fortran Compiler XE 14.0.2 | ||
| - | * Intel® Debugger 13.0 Update 1 (for Linux* OS only) | ||
| - | * GNU* Project Debugger (GDB*) 7.5 | ||
| - | * Intel® Integrated Performance Primitives 8.0 Update 1 | ||
| - | * Intel® Threading Building Blocks (TBB) 4.2 | ||
| - | * Intel® Math Kernel Library (MKL) 11.1 | ||
| - | * Intel® MPI Library 4.1 Update 1 | ||
| - | * Intel® Trace Analyzer and Collector 8.1 Update 3 | ||
| - | | ||
| - | ====== Compiling Applications ====== | ||
| - | |||
| - | < | ||
| - | |||
| - | Before you start compiling your application, | ||
| - | |||
| - | < | ||
| - | |||
| - | module load intel/ | ||
| - | |||
| - | </ | ||
| - | |||
| - | |||
| - | **Sequential programs** : '' | ||
| - | |||
| - | |||
| - | < | ||
| - | |||
| - | Compiler command line: | ||
| - | |||
| - | <code bash> | ||
| - | $ icc [options] myprogram.c -o myprogram | ||
| - | </ | ||
| - | |||
| - | ===== Compilers Options ===== | ||
| - | |||
| - | Selected Intel compiler options: | ||
| - | |||
| - | ^Option^Description^ | ||
| - | |-O0|Disables all optimizations. Recommended for program development and debugging| | ||
| - | |-O1|Enables optimization for speed, while being aware of code size (e.g no loop unrolling)| | ||
| - | |-O2|Default optimization. Optimizations for speed, including global code scheduling, software pipelining, predication, | ||
| - | |-fast|Shorthand. '' | ||
| - | |**-O3**|-O2 optimizations plus more aggressive optimizations such as prefetching, | ||
| - | |**-axAVX**|This option tells the compiler to generate multiple, processor-specific auto-dispatch code paths for Intel processors if there is a performance benefit. It also generates a baseline code path which can run on non-AVX processors. The Intel processor-specific auto-dispatch path is usually more optimized than the baseline path.| | ||
| - | |-p |Compiles and links for function profiling with gprof.| | ||
| - | |-g| Produces a symbol tables, i.e. line numbers for profiling are available.| | ||
| - | |-openmp|Enables the parallelizer to generate multithreaded code based on OpenMP directives.| | ||
| - | |-parallel|Tells the auto-parallelizer to generate multithreaded code for loops that can be safely executed in parallel. To use this option, you must also specify -O2 or -O3.| | ||
| - | |-opt_report|generate an optimization report to stderr.| | ||
| - | |** -fp-model precise**| Allow users to trade off floating point optimizations for accuracy and consistency. Intel recommends specifying '' | ||
| - | |**-pc 64**|Force the compiler to use floating double precision (53-bit mantissa) to ensure the portability of results.| | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | Because processors of cluster Lumière are '' | ||
| - | |||
| - | <WRAP center round box 20%> | ||
| - | |||
| - | |||
| - | <color blue> | ||
| - | </ | ||
| - | |||
| - | <note important> | ||
| - | |||
| - | if your application is sensitive to the to the accuracy of the precision, or fractional part of the floating-point | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | ==== Examples : ==== | ||
| - | |||
| - | |||
| - | |||
| - | Compile a C program | ||
| - | |||
| - | <code bash> | ||
| - | $ icc -axAVX | ||
| - | </ | ||
| - | |||
| - | Compile a Fortran program | ||
| - | |||
| - | <code bash> | ||
| - | $ ifort -axAVX | ||
| - | </ | ||
| - | |||
| - | Compiler a C++ program | ||
| - | |||
| - | <code bash> | ||
| - | $ icpc -axAVX | ||
| - | </ | ||
| - | |||
| - | |||
| - | Compile an OpenMP program written inc C | ||
| - | |||
| - | <code bash> | ||
| - | $ icpc -openmp -axAVX -O3 -fp-model precise -pc 64 pgm.cpp -o pgm | ||
| - | </ | ||
| - | |||
| - | Compiler an OpenMP program written in Fortran | ||
| - | |||
| - | <code bash> | ||
| - | $ ifort -openmp -axAVX | ||
| - | </ | ||
| - | ====== Vectorization ====== | ||
| - | The Intel compiler has several options for vectorization. One option is the -x flag, which tells the compiler to generate specific vectorization instructions. The -x flag takes a mandatory option, which can be AVX (i.e., -xAVX), SSE4.2, SSE4.1, SSE3, SSE2, etc. The processor on which a user runs must support the vectorization instructions specified. To determine what is supported, examine the / | ||
| - | |||
| - | The Intel compiler can generate a single executable with multiple levels of vectorization with the -ax flag, which takes the same options as the -x flag (i.e., AVX, ..., SSE2). This flag will generate run-time checks to determine the level of vectorization support on the processor and will then choose the optimal execution path for that processor. It will also generate a baseline execution path that is taken if the -ax level of vectorization specified is not supported. The baseline can be defined with the -x flag, with -xSSE2 recommended. | ||
| - | |||
| - | Another useful option for the Intel compiler is the -vec-report flag, which generates diagnostic information regarding vectorization to stdout. The -vec-report flag takes an optional parameter that can be a number between 0 and 5 (e.g., -vec-report0), | ||
| - | |||
| - | Refer to the man pages or the compiler documentation for more details about these options. | ||
| - | |||
| - | |||
| - | ====== Links ====== | ||
| - | |||
| - | * http:// | ||