UAntwerp Intel toolchains¶
From version 2017a on of the Intel toolchains, the setup on the UAntwerp is different from the one on some other VSC clusters:
A full install of all Intel tools for which we have a license at UAntwerp has been performed in a single directory tree as intended by Intel. There is a single module for the C/C++/Fortran compilers, Intel MPI, the libraries MKL (Math Kernel Library), IPP (Integrated Performance Primitives), TBB (Threading Building Blocks) and DAAL (Data Analytics Acceleration Library) and Intel-provided GDB-based debuggers. The Intel tools for code and performance analysis VTune Amplifier XE, Intel Trace Analyzer and Collector (ITAC), Intel Advisor XE and Intel Inspector XE are also installed, but these still have separate module files as they rely on overloading libraries in some cases.
There should be no need to run any of the configuration scripts provided by Intel, all variables should be set correctly by the module file. Contact user support if this is not the case. The configuration scripts should work as intended by Intel though should you want to use the compilers without loading the module.
Several variables specific for the way software is set up at the VSC are defined the way they would be defined if the Intel toolchain was defined in the standard VSC way through the module tree. As such, we expect that you should be able to use any Makefile developed for the standard VSC-setup.
All compiler components needed to develop applications with offload to a Xeon Phi expansion board are also provided (for the compiler versions that support the Xeon Phi).
Compilers¶
The compilers work exactly in the way described on the regular Intel toolchain web page, including the MPI compiler wrappers. All links to the documentation on that page are also relevant.
Man pages for all commands have also been installed.
Debuggers¶
Intel-adapted GDB debuggers have been installed
Debugging regular Intel64 applications:
gdb-ia
Debugging applications with offload to Xeon Phi:
gdb-mic
Manual pages and GNU info pages are available for both commands
Libraries¶
Math Kernel Library (MKL)¶
MKL works exactly as in the regular VSC Intel toolchain. See the MKL section of web page on the VSC Intel toolchain for more information.
Integrated Performance Primitives (IPP)¶
What? The Intel Integrated Performance Primitives is a software library that provides a broad range of functionality, including general signal and image processing, computer vision, data compression, cryptography, and string manipulation. The functions are heavily optimised for the Intel processors.
Documentation
Getting started with Intel® Integrated Performance Primitives for Linux* OS
Developer guide and various tutorials in the Intel Software Documentation Library
Threading Building Blocks (TBB)¶
What? A C++ template library for task parallelism. The library is developed by Intel, but now available under the Apache 2.0 license and runs also with non-Intel compilers, so you don’t have to be concerned about vendor lock-in.
Documentation
Documentation in the Intel Software Documentation Library
Data Analytics Acceleration Library (DAAL)¶
What? A library with building blocks covering all stages of data analytics: data acquisition from a data source, pre-processing, transformation, data mining, modelling, validation, and decision making. The implementation is heavily optimised for Intel processors.
Documentation
Code and performance analysis¶
VTune Amplifier XE¶
What? VTune Amplifier is a tool for runtime analysis of serial and shared memory applications. For a list of features, please consult the Getting Started with VTune web page.
Module:
inteldevtools/<toolchain version>
, e.g.,inteldevtools/2017a
.How? VTune Amplifier is started through the
amplxe-gui
(GUI version) oramplxe-cl
(command line version) command.Documentation:
Intel VTune Amplifier documentation in the Intel Software Documentation Library
Man page for
amplxe-cl
(after loading the appropriate VTune module)
ITAC - Intel Trace Analyzer and Collector¶
What? ITAC is a graphical tool to understand MPI application behaviour. A full set of features can be found on the Getting Started with Intel Trace Analyzer and Colllector page.
How? Analysis is a two-step operation:
Run your application using the
-trace
option of mpirun to collect data in a.stf
file.Analyse the data using
traceanalyzer
Module:
inteldevtools/<toolchain version>
, e.g.,inteldevtools/2017a
.Documentation:
Getting started with Intel Trace Analyzer and Collector on the Intel web site
Intel Trace Analyzer and Collector documentation in the Intel Software Documentation Library
Manual pages for the library functions and some commands
Advisor¶
What? Advisor is a code analysis tool that works with the compilers to give advise on vectorization and threading for both the Xeon and Xeon Phi processors.
How? Advisor uses output generated by the compiler when building a full optimized release build and as such expects that some additional options are specified when compiling the application. The resulting compiler output can then be analysed using the
advixe-gui
command.Module:
inteldevtools/<toolchain version>
, e.g.,inteldevtools/2017a
.Documentation
Intel Advisor documentation in the Intel Software Documentation Library
Manual page for
advixe-cl
Inspector¶
What? Inspector is a run-time analysis error checking tool for dynamic memory and threading errors.
How? Inspector uses a debug build of you application. The application is run from within Inspector. Inspector can be started with the
inspxe-gui
(GUI version) orinspxe-cl
(Command Line version) command.Module:
inteldevtools/<toolchain version>
, e.g.,inteldevtools/2017a
.Documentation:
Further Intel Inspector documentation in the Intel Software Documentation Library
Manual page for
inspxe-cl