Development/Intel Compiler
|
The main documentation is available via |
| Description | Content |
|---|---|
| module load | compiler/intel/VERSION and compiler/intel/VERSION_llvm |
| License | Commercial. See $INTEL_HOME/install-doc/EULA.txt. | Intel Product Licensing FAQ |
| Citing | n/a |
| Links | Intel C-Compiler Homepage |
| Graphical Interface | Yes (Intel Debugger GUI-Verison) |
| Included modules | icc | icpc | ifort | idb | gdb-ia |
Introduction
The Intel Compiler consists of tools to compile and debug C, C++ and Fortran programs, and currently is in a transition phase: the so-called legacy compiler (based on an Intel in-house development with many optimization hints) and the newer LLVM-based compiler (where many of these optimizations and hints are ported to). To smoothly handle this transition we offer the standard legacy compiler plus the new LLVM-based compiler with the _llvm prefix. The following table shows the preferred names:
| Tool | Legacy name | LLVM-based name |
| Intel C compiler | icc | icx |
| Intel C++ compiler | icpc | icpx |
| Intel Fortran compiler | ifort | ifx |
| Intel debugger in GUI mode (until version 14 only) | idb | N/A |
| Intel GNU debugger in console mode (from version 15) | gdb-ia | gdb-oneapi |
| Intel debugger in console mode (until version 14 only) | idbc | N/A |
The intel compiler suite also includes the TBB (Threading Building Blocks), IPP (Integrated Performance Primitives) and oneAPI libraries.
More information about the MPI versions of the Intel Compiler is available here:
Documentation
Online documentation
Optimizations
You can turn on various optimization options to enhance the performance of your program. Which options are the best depends on the specific program and can be determined by benchmarking your code. A command which gives good performance and a decent file size is
icx -xHost -O2 ex.c.
With the option -xHost instructions for the highest instruction set available on the compilation host processor are generated. If you want to generate optimal code on bwUniCluster for both nodes with Sandy Bridge architecture and nodes with Broadwell architecture, you must compile your code with the options -xAVX -axCORE-AVX2 (instead of -xHost).
There are more aggressive optimization flags and levels (e.g. -O3 or -fast and implied options) but the compiled programs can get quite large due to inlining. Additionally the compilation process will probably take longer. Moreover it may happen that the compiled program is even slower -- or may require installation of additional statically-linked libraries. Such a command would be for example:
icx -fast ex.c
Profiling
Profiling an application means augmenting the compiled binary with information on execution counts per source-line (and basic blocks) -- e.g. one may see how many times an if-statement has been evaluated to true. To do so, compile your code with the profile flag:
icx -p ex.c -o ex.
Using the gprof tool, one may manually inspect execution count of each executed line of source code.
For compiler optimization, recompile your source using
icx -prof-gen ex.c -o ex
then execute the most co]]mmon and typical use-case of your application, and then recompile using the generated profile count (and using optimization):
icx -prof-use -O2 ex.c -o ex.
Further literature
A tutorial on optimization can be found at Vectorization Essentials
and to get the different optimization options execute
icx -help opt
or
icx -help advanced
or the previously described catch-all option -v --help.