Fortran READ returns iostat=98 error
Fortran READ statement can return an out of memory error if there is not enough virtual memeory. Author: Elizabeth S (Intel) Type: Errors and Diagnostics |
10/30/2009
|
Diagnostic 5656: Variable xxxx too large for NTCOFF. Bigger than 2GB. Use heap instead
2 GByte limit on static and data areas in COFF object file format. Author: Steve D. (Intel) Type: Errors and Diagnostics |
10/19/2009
|
Diagnostic 11003: no IR in object file xxxx; was the source file compiled with xxxx
You are attempting to link an object file that was not compiled with IPO in and IPO build.
Author: Mark Sabahi (Intel) Type: Errors and Diagnostics |
09/16/2009
|
Diagnostic 5418: USEROPEN routine must be defined with C or Default calling convention
Description of Fortran error 5418: USEROPEN routine must be defined with C or Default calling convention Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
09/14/2009
|
Diagnostic 6502: COMMON cannot be extended beyond the beginning of a block.
Description of Fortran error 6502: COMMON cannot be extended beyond the beginning of a block Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
09/11/2009
|
Parallel Debugger Extension Exceptions: 0xa1a01db1, 0xa1a01db2
When run under the VS2005 debugger, code compiled with Qopenmp display exceptions:
First-chance exception at 0x7c812afb in Parallel_bug.exe: 0xA1A01DB1: 0xa1a01db1.
First-chance exception at 0x7c812afb in Parallel_bug.exe: 0xA1A01DB2: 0xa1a01db2.
Author: Roland Wiele (Intel) Type: Errors and Diagnostics |
09/08/2009
|
Diagnostic 6405: The same named entity from different modules and/or program units cannot be referenced.
Information about Fortran diagnostic (error) 6405: The same named entity from different modules and/or program units cannot be referenced. Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/31/2009
|
Error 6405 with interface checking and EXTERNAL declaration in module
Reference Number : DPD200139304Version : 11.1Operating System : AllProblem Description : The compiler will incorrectly issue diagnostic 6405: The same named entity from different modules and/or progr ... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/31/2009
|
Diagnostic 8068: If the language-binding-spec has a NAME= specifier
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
Diagnostic 8069: This symbol has multiple BIND statement/attribute declarations which is not allowed.
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
Diagnostic 8070: The ASYNCHRONOUS= specifier in a data transfer statement must be a character initialization expression (Constraint C924).
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
Diagnostic 8071: An integer constant expression is required in this context; the directive will be ignored.
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
Diagnostic 8072: This keyword is invalid for the LOOPCOUNT directive; the directive will be ignored.
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
Diagnostic 8073: The LOOPCOUNT directive only allows 1 MIN
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
Diagnostic 8074: The LOOPCOUNT directive with keywords is not supported in this release; the directive will be ignored.
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
Diagnostic 8075: The argument ISHIFT to the SHIFTR/SHIFTL intrinsic function is out-of-range.
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
Diagnostic 8076: A proc-language-binding-spec is not standard Fortran xx.
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
Diagnostic 8077: A proc-language-binding-spec shall not be specified for an internal procedure.
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
Diagnostic 8078: A derived type with the BIND attribute is not standard Fortran xx.
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
Diagnostic 8079: A derived type with the BIND attribute shall not be SEQUENCE type
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
Diagnostic 8080: Each component of a derived type with the BIND attribute shall be a nonpointer
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
Diagnostic 8081: The variable with the BIND(C) attribute shall not appear in common block.
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
Diagnostic 8082: The NULLIFY attribute may only be used for a dummy argument that has both the POINTER and INTENT(OUT) attributes.
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
Diagnostic 8083: The DLLEXPORT attribute should not be specified for a type.
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
Diagnostic 8084: An internal file unit must be of type character.
... Author: Steve Lionel (Intel) Type: Errors and Diagnostics |
08/27/2009
|
