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."
This page lists fixes that have been made in Intel Professional Edition Compilers 11.1.
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.
The upcoming OpenMP 4.0 will be discussed at SC12, and there wil
[Updated based on the version of update 2 of 2013 SP1]
Intel MKL 11.3 has introduced Intel TBB support.