Using MKL, the Intel Math Kernel Library (v11.0.0.079) - ICHEC

Static/Dynamic LinkingIntel MKL supports both linking models static ordynamic. Each of them has their pros and cons. Staticlinking resolves all symbolic references at link time. Thebehaviour of statically built executables is predictable,because there are no run-time dependencies. The maindisadvantage is that having to relink new versions of thelibrary to your application may be error-prone and timeconsuming,because you have to relink the entireapplication. Moreover, static linking results in largeexecutables and uses memory less efficiently. If severalexecutables are linked with the same library, each of themmust load it into memory independently. This matters mostfor executables having data sizes that are small andcomparable with the size of the executable.Dynamic linking postpones the resolution of someundefined symbolic references until run time. Dynamicallybuilt executables contain those symbols along with a list oflibraries that provide definitions of the symbols. When theexecutable is loaded, the final linking is done before theapplication runs. If several dynamically built executablesreference the same library, it is loaded into memory onlyonce and the executables share it, thereby saving memory.Dynamic linking enables you to separately update thelibraries on which applications depend and does notrequire relinking the applications. The developmentadvantages of dynamic linking are achieved at some costto performance, because every unresolved symbol has tobe looked up in a dedicated table and resolved at runtime.Linking SyntaxDynamic Case -L$MKLPATH -I$MKLINCLUDE[-lmkl_blas{95_ilp64|95_lp64}][-lmkl_lapack{95_ilp64|95_lp64}][ ]-lmkl_{intel_ilp64|intel_lp64|intel_sp2dp|gf_ilp64|gf_lp64}-lmkl_{intel_thread|gnu_thread|pgi_thread|sequential}-lmkl_core[-liomp5] [-lpthread] [-lm] [-ldl]Static Case -L$MKLPATH -I$MKLINCLUDE[$MKLPATH/libmkl_blas{95_ilp64|95_lp64}.a][$MKLPATH/libmkl_lapack{95_ilp64|95_lp64}.a]-Wl,--start-group[ ]$MKLPATH/libmkl_{intel_ilp64|intel_lp64|intel_sp2dp|gf_ilp64|gf_lp64}.a$MKLPATH/libmkl_{intel_thread|gnu_thread|pgi_thread|sequential}.a$MKLPATH/libmkl_core.a-Wl,--end-group[-liomp5] [-lpthread] [-lm] [-ldl]Notes: {a,b,c} only one of the libraries should be chosen, [a] optional. On stokes and stoney$MKLPATH=$MKLROOT/lib/intel64$MKLINCLUDE=$MKLROOT/include5