Diagnostic 6754: An automatic object must not appear in a SAVE statement or be declared with the SAVE attribute.
Explanation of Intel Fortran error #6754 An automatic object must not appear in a SAVE statement or be declared with the SAVE attribute. Type: Errors and Diagnostics |
Fortran |
03/30/2012
|
Intel compiler and Xcode 3.2.2 linker - binary runtime crash with switch statement
Attempting to run the 64-bit binary built with Intel compiler and Xcode 3.2.2 or newer on a Mac OS X 10.6.3 32-bit kernel result in a segmentation fault. Type: Errors and Diagnostics |
crash 3.2.2 3.2.3 64 ClosedSWDefect |
02/06/2012
|
Diagnostic 7836: If the actual argument is scalar, the corresponding dummy argument shall be scalar unless the actual argument is an element of an array that is not an assumed-shape or pointer array, or a substring of such an element.
Description of Intel Fortran Compiler Error #7836: If the actual argument is scalar, the corresponding dummy argument shall be scalar... Type: Errors and Diagnostics |
|
01/27/2012
|
Using the IDB Debugger under Mac OS* X 10.7 Lion
IDB use under Mac OS* X Lion Type: Errors and Diagnostics |
idb |
01/17/2012
|
Diagnostic 6633: The type of the actual argument differs from the type of the dummy argument.
Description of Intel Fortran error #6633: The type of the actual argument differs from the type of the dummy argument. Type: Errors and Diagnostics |
|
11/30/2011
|
-staticlib option bug in Intel Compiler version 12.1.1.246 aka Update 7
bug in -staticlib option to Intel Composer XE 2011 for Mac OS X Update 7 Type: Errors and Diagnostics |
|
11/08/2011
|
Determining Root Cause of Segmentation Faults SIGSEGV or SIGBUS errors
SIGSEGV on linux and SIGBUS Root Causes Type: Errors and Diagnostics |
|
09/29/2011
|
Don't use the OpenMP THREADPRIVATE 'compatibility' option when everything is compiled by Intel
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. Type: Errors and Diagnostics |
OpenMP THREADPRIVATE compatibility |
08/25/2011
|
Running an Intel-compiled binary on older Mac OS X system gives dyld: unknown required load command 0x80000022
dyld: unknown required load command 0x80000022
Type: Errors and Diagnostics |
|
04/29/2011
|
Diagnostic 5436: Overlapping storage initializations encountered with xxxx
Explanation of Intel Fortran Compiler warning 5436. Type: Errors and Diagnostics |
|
02/15/2011
|
Description of PARDISO errors and messages
The Articles provides the detailed description of errors and messages returned by Pardiso. Type: Errors and Diagnostics |
pardiso PARDISO message in-core calculation out-of-core (OOC) mode |
01/19/2011
|
Don't optimize when using -ftrapuv for uninitialized variable detection
The switch /Qtrapuv (-ftrapuv) for detecting certain uninitialized variables is designed to work with optimization disabled Type: Errors and Diagnostics |
uninitialized |
12/23/2010
|
error #7859: THREADPRIVATE entity not allowed with DEFAULT(SHARED) clause
Intel Fortran Composer XE 2011 generates bogus compilation error #7859 when a THREADPRIVATE entity is referenced in a parallel region which has been annotated with a DEFAULT(SHARED) clause. Type: Errors and Diagnostics |
|
12/13/2010
|
GAP Message - remark #30532: (LOOP) Store the value of the upper-bound expression (foo->len) of the loop at line 123 into a temporary local variable...
Message
Store the value of the upper-bound expression (foo->len) of the loop at line 123 into a temporary local variable, and use this variable as the new upper-bound expression of the loop. To ... Type: Errors and Diagnostics |
GAP |
10/17/2010
|
GAP Message - remark #30531: (LOOP) Store the value of the upper-bound expression of the loop into a temporary local variable...
Message
Store the value of the upper-bound expression of the loop at line 123 into a temporary local variable, and use this variable as the new upper-bound expression of the loop. To do this, inse ... Type: Errors and Diagnostics |
GAP |
10/17/2010
|
GAP Message - remark #30528: (PAR) Add ""__declspec(const)" to the declaration of routine "foo" in order to parallelize the loop at line 123
Message
Add "__declspec(const)" to the declaration of routine "foo" in order to parallelize the loop at line 123. Alternatively, adding "__declspec(concurrency_safe(profitable))" achieves a simila ... Type: Errors and Diagnostics |
GAP |
10/17/2010
|
GAP Message - remark #30526: (PAR) To parallelize the loop, annotate the routine "foo" with ""__declspec(const)"
Message
To parallelize the loop at line 123, annotate the routine "foo" with "__declspec(const)". [VERIFY] Make sure the routine satisfies the semantics of this annotation. [ALTERNATIVE] A weaker ... Type: Errors and Diagnostics |
GAP |
10/17/2010
|
Problem with Intel(R) MKL DSS Single Precision version
The F90 DSS interface is broken because of currently DSS API supports double precision data types only.
Type: Errors and Diagnostics |
MKL F90 Single Precision |
10/12/2010
|
GAP Message - remark #30533: (LOOP) Compile with the "-Qopt-subscript-in-range" option to vectorize and/or parallelize the loop
Message
Compile with the "-Qopt-subscript-in-range" option to vectorize and/or parallelize the loop at line 123. [VERIFY] Make sure that no loop in the program contains or generates very large int ... Type: Errors and Diagnostics |
|
09/02/2010
|
GAP Message - remark #30525: (PAR) Insert a "#pragma loop count min(128)" or "!dir$ loop count min(128)" statement right before the loop to parallelize the loop
Message
Insert a "#pragma loop count min(128)" or "!dir$ loop count min(128)" statement right before the loop at line 123 to parallelize the loop. [VERIFY] Make sure that the loop has a minimum of ... Type: Errors and Diagnostics |
GAP |
09/02/2010
|
GAP Message - remark #30522: (PAR) Insert a "#pragma parallel private(foo)" or "!dir$ parallel private(foo)" statement right before the loop to parallelize the loop
Message
Insert a "#pragma parallel private(x,y,z)" statement right before the loop at line 123 to parallelize the loop. [VERIFY] Before an element of array(s) "x,y,z" can be read in the loop, ther ... Type: Errors and Diagnostics |
GAP |
09/02/2010
|
GAP Message - remark #30519: (PAR) Insert a "#pragma parallel" or "!dir$ parallel" statement right before the loop to parallelize the loop
Message
Insert a "#pragma parallel" or "!dir$ parallel" statement right before the loop at line 123 to parallelize the loop. [VERIFY] Make sure that these arrays in the loop do not have cross-iter ... Type: Errors and Diagnostics |
GAP |
09/02/2010
|
GAP Message - remark #30515: (VECT) Assign a value to the variable(s) at the beginning of the body of the loop...
Message
Assign a value to the variable(s) "foo" at the beginning of the body of the loop in line 123. This will allow the loop to be vectorized. [VERIFY] Make sure that, in the original program, t ... Type: Errors and Diagnostics |
GAP |
09/02/2010
|
GAP Message - remark #30513: (VECT) Insert a "#pragma ivdep" or "!dir$ ivdep" statement right before the loop to vectorize the loop
Message
Insert a "#pragma ivdep" or "!dir$ ivdep" statement right before the loop at line 123 to vectorize the loop. [VERIFY] Make sure that these arrays in the loop do not have unsafe cross-itera ... Type: Errors and Diagnostics |
GAP |
09/02/2010
|
GAP Message - remark #30506: (VECT) If the following operations(s) can be safely performed unconditionally...
Message
If the following operations(s) can be safely performed unconditionally, the loop at line 123 will be vectorized by adding a "#pragma ivdep" or "!dir$ ivdep" statement right before the loop ... Type: Errors and Diagnostics |
GAP |
09/02/2010
|
