In very large, complex functions, loops preceded by OpenMP directives may not be threaded. Compiler may emit the warning remark: "An internal threshold was exceeded: loops may not be vectorized or parallelized. Try to reduce routine size."
Compiling an application with the -openmp option that does not contain OpenMP pragmas causes a segmentation fault due to stack size overrun.
This page lists fixes that have been made in Intel Professional Edition Compilers 11.1.
Advice and background information is given on typical issues that may arise when threading an application using the Intel Fortran Compiler and other software tools, whether using OpenMP, automatic parallelization or threaded libraries.
This note explains how to configure the Weather Research & Forecasting (WRF) run-time environment in order to achieve best performance and scalability on Intel® architecture with Intel® software tools.
The multi-core performance of a legacy Fortran benchmark unsuited to data parallelism is enhanced by threading using the TASK construct of OpenMP and the Intel Fortran Compiler. The necessary source code changes are explained in detail.
This article explains how to create your own OpenMP* thread mapping to OS proc IDs with Intel® C/C++ and Fortran compiler, by setting environment variable KMP_AFFINITY. It also provides some thread affinity demo results on when use different settings.
The Intel C++ and Fortran compilers for Windows* and Linux* provide 'legacy' and 'compatibility' implementations of the OpenMP THREADPRIVATE directive. The 'compatibility' option should not be used when everything is compiled by Intel compilers.
The newest releases of the Intel® C++ and Fortran Compilers support new features in the OpenMP* 3.1 Specification
An application compiled with -Qopenmp (Windows*)/-openmp (Linux*) and run on a host not containing a genuine Intel® processor may generate bogus OMP: Warning #71 and Warning #72.