Article

Diagnostic 1392: variable "entity" in firstprivate or lastprivate clause of an OpenMP pragma must be shared in the enclosing context

CauseOne case that the Intel C++ Compiler will emitting this diagnostic message is when using the "firstprivate" of OpenMP* with a wrong syntax.

Authored by admin Last updated on 05/25/2018 - 15:30
Article

OMP: Error #15: Initializing libguide.lib, but found libguide40.dll already initialized.

Linker error generated when different parts of a program try to link both the static and dynamic versions of the OpenMP runtime. The solution is to expilcitly call out either a dynamic or static link.
Authored by Last updated on 12/26/2018 - 11:33
Article

internal threshold was exceeded

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."
Authored by Martyn Corden (Intel) Last updated on 12/26/2018 - 13:11
Article
Article

Diagnostic 15011: loop was not vectorized: statement cannot be vectorized

Cause:

Authored by admin Last updated on 05/25/2018 - 15:30
Article

Diagnostic 15018: loop was not vectorized: not inner loop

Cause: Always the inner loop is targeted for vectorization and outer loop is targeted for parallelization. Below is an example for this scenario. 

Authored by admin Last updated on 05/25/2018 - 15:30
Article

Using Intel® Debugger for Linux* on the Command Line

Use the command "idbc" to start the command line version of Intel® Debugger for Linux*
Authored by admin Last updated on 06/07/2017 - 12:04
Article

Diagnostic 15015: loop was not vectorized: unsupported data type

Cause:

Authored by admin Last updated on 05/25/2018 - 15:30
Article

Diagnostic 15003: xxxx WAS VECTORIZED

There can be mutiple variants of this diagnostic: 1. PARTIAL LOOP WAS VECTORIZED 2. OpenMP SIMD LOOP WAS VECTORIZED  3. REMAINDER LOOP WAS VECTORIZED

Authored by admin Last updated on 05/25/2018 - 15:30
Article

Tips for Debugging Run-time Failures in Intel Fortran Applications

Run-time crashes can be slow and hard to debug. Use compiler options to get more information about such failures before starting time-consuming interactive debugging.
Authored by admin Last updated on 12/26/2018 - 11:09