That will tell you whether you hit a bug related to aggressive compiler optimization. If you experience crashes, it is always worth trying to recompile with lower optimization ( -O1) or no optimization at all ( -O0). We recommend trying these compiler flags as a start: System We have often seen that high optimization can uncover silent bugs in the code, often as a result of the program relying on undefined Fortran or C behavior. Some of them are very aggressive and can lead instability and/or crashes when applied on fragile code.
Intel's compiler have many options and compiler flags for optimization. More information about using MKL and the other math libraries at NSC is available in the math libraries page. The -Nmkl flag is specific to NSC and links your program permanently against the currently loaded Intel MKL module, the other flag -mkl=sequential is specific to Intel's compilers and assembles the right combination of libraries necessary for single-threaded MKL linking. If your program uses BLAS, LAPACK, or FFTW, we recommend using the subroutines included in Intel's Math Kernel Library: ifort -o myprogram.exe -Nmkl -mkl=sequential myprogram.f90 That will produce the executable myprogram.exe with optimization level -O2 (see more below). Do like this: ifort -o myprogram.exe myprogram.f90 Suppose you have a file myprogram.f90 that you want to compile. The compilers for different programming languages are named as follows: Language Instead, just load the corresponding compiler module, and everything gets set up correctly.
We do not recommend that you source the normal compiler initialization scripts named compilervars.sh or similar. Intel's compilers are installed in /software/intel (older versions) and /software/apps/intel.
0 kommentar(er)
