Back to All Intel Fortran Compiler Diagnostics

• 6500: A bound in an allocate-shape-spec involves array inquiry about allocate-object in same ALLOCATE statement.
• 6501: The equivalences are causing alignment problems.
• 6502: COMMON cannot be extended beyond the beginning of a block.
• 6503: This keyword is invalid for this intrinsic procedure reference.
• 6504: Non-keyword arguments are invalid after keyword arguments have been encountered.
• 6505: This intrinsic procedure reference contains too few arguments.
• 6506: This intrinsic procedure reference contains too many arguments.
• 6507: This intrinsic procedure reference is missing a required argument.
• 6508: This keyword must not be used more than once in an intrinsic procedure reference.
• 6509: An array name as a variable is invalid in this context.
• 6510: NAMELIST group name is required here.
• 6511: This DO variable has already been used as an outer DO variable in the same nesting structure.
• 6512: A scalar-valued expression is required in this context.
• 6513: An array-valued expression is required in this context.
• 6514: A substring must be of type CHARACTER.
• 6515: This function, which is specified as the left side of an assignment statement, is invalid.
• 6516: This attribute specification is not valid for a component definition statement.
• 6517: Nested derived type definitions are not permitted.
• 6518: An external, internal, or module function reference is invalid in a specification expression.
• 6519: This intrinsic function reference is invalid in specification expressions.
• 6520: A PRIVATE statement within a derived type definition cannot have a list of names attached to it
• 6521: Only one of the selectors of one of the CASE statements may be DEFAULT.
• 6522: A CASE statement must not be a branch target statement.
• 6523: It is illegal to branch out of a DO loop associated with a PPD PDO or PARALLEL DO directive.
• 6524: A SEQUENCE statement is permitted only within a derived type definition block
• 6525: An array section is not valid for list-oriented data.
• 6526: A branch to a do-term-shared-stmt has occurred from outside the range of the corresponding inner-shared-do-construct.
• 6527: This object has been initialized more than once.
• 6528: Because the actual argument is a label, the associated dummy argument must be specified by an asterisk (*).
• 6529: Because the dummy argument is specified by an asterisk (*), the associated actual argument must be a label.
• 6530: The array spec for this component must be of explicit shape and each bound must be an initialization expression.
• 6531: The character length in a component declaration must be a constant expression.
• 6532: The percent character (%) has been used incorrectly.
• 6533: Since no POINTER attribute has been specified for this component, the type of this component cannot be same as the derived type being defined.
• 6534: A derived type name can not be the same as the name of any intrinsic type
• 6535: This variable or component must be of a derived or structure type
• 6536: All symbols from this module are already visible due to another USE; the ONLY clause will have no effect. Rename clauses, if any, will be honored.
• 6537: This must be an array section or array constructor of rank 1.
• 6538: RESULT clause on ENTRY statements must be in function subprogram.
• 6539: This VFE is not supported in a character format specifier.
• 6540: This directive is not (yet) supported.
• 6541: This element is not yet supported in this context.
• 6542: An array section or array constructor is required for the ORDER and MOLD arguments.
• 6543: The size of the ORDER and MOLD arguments must be a constant.
• 6544: The size of the ORDER and MOLD arguments must be in the range: 0 < size < 8.
• 6545: For the RESHAPE intrinsic function, the size of the ORDER argument must equal the size of the MOLD argument.
• 6546: A required END statement for the interface-body is missing.
• 6547: The ARRAY argument of the ALLOCATED inquiry intrinsic function shall be an allocatable array.
• 6548: A subroutine or function may be calling itself recursively.
• 6549: An arithmetic or LOGICAL type is required in this context.
• 6550: If an actual argument is an intrinsic procedure, that intrinsic procedure name must appear in an INTRINSIC statement.
• 6551: This intrinsic procedure cannot be passed as an actual argument.
• 6552: The CALL statement is invoking a function subprogram as a subroutine.
• 6553: A function reference is invoking a subroutine subprogram.
• 6554: This subscript is out-of-range.
• 6555: When a value is signed, a literal constant is required.
• 6556: This array declaration is invalid.
• 6557: An =initialization-expr is missing; an initialization expression is required when using the PARAMETER attribute.
• 6558: The quoted string must contain at least one character.
• 6559: The END= specifier is invalid in an indexed READ statement.
• 6560: A key-of-reference specifier must not exist without a key-specifier.
• 6561: An external function name is required in this context.
• 6562: A data initialization-expr is not valid for this object.
• 6563: A component with POINTER attribute may NOT be to the right of an array component (6.1.2).
• 6564: For an indexed READ statement, the type or sort for the key specifier expression is invalid.
• 6565: The syntax of the list specified by OPEN KEY= is invalid.
• 6566: An element within the list specified by OPEN KEY= is invalid.
• 6567: In an OPEN statement, the only valid keywords of the KEY= specifier that specify the data type are INTEGER or CHARACTER.
• 6568: This use of the ADVANCE, SIZE, or EOR specifier is invalid.
• 6569: This requires scalar arguments and a scalar result.
• 6570: This attribute specification is incomplete.
• 6571: This attribute specification must be a single keyword.
• 6572: In an OPEN statement, the only valid directional keywords for the KEY= specifier are ASCENDING or DESCENDING.
• 6573: An assignment to a DO variable within a DO body is invalid.
• 6574: The name of a COMMON block that does not exist appears in the VOLATILE statement.
• 6575: An object appears more the once in the same or different VOLATILE statements.
• 6576: If a namelist-group-name has the PUBLIC attribute, no item in the namelist-group-object-list may have the PRIVATE attribute.
• 6577: The expression to the right of the equals sign (=) is invalid for this keyword.
• 6578: A NAMELIST group object must not be an allocatable object, a pointer, or a variable of a type that has an ultimate component that is a pointer or an allocatable array.
• 6579: A dummy argument of a statement function is invalid in this context.
• 6580: Name in only-list does not exist.
• 6581: Unresolved rename.
• 6582: A dummy argument which has the OPTIONAL or the INTENT(OUT) attribute is not allowed in this specification expression.
• 6583: In specification expressions, dummy arguments must have the INTENT(IN) attribute.
• 6584: The encompassing structure of a field cannot be an array name in this context.
• 6585: SIZE of array is not computable.
• 6586: An assumed-shape array, an assumed-size array, or a passed-length variable of type CHARACTER is not valid in this context.
• 6587: Upper Bound of array is not computable.
• 6588: An automatic object must not be of type CHARACTER.
• 6589: An INTERFACE block must include a FUNCTION or SUBROUTINE statement.
• 6590: This statement is not permitted as a statement within a derived-type-def
• 6591: An automatic object is invalid in a main program.
• 6592: This symbol must be a defined parameter, an enumerator, or an argument of an inquiry function that evaluates to a compile-time constant.
• 6593: The number of expressions in a structure constructor differs from the number of components of the derived type
• 6594: The rank of an element in a structure constructor differs from the rank of the component of the derived type
• 6595: The shape of an element in a structure constructor differs from the shape of the component of the derived type
• 6596: If a deferred-shape array is intended, then the ALLOCATABLE or POINTER attribute is missing; if an assumed-shape array is intended, the array must be a dummy argument.
• 6597: Logical and numeric arguments must not be mixed.
• 6598: A CHARACTER array assignment is invalid.
• 6599: Hollerith count within a character format-specifier is incorrect.
• 6600: Only one explicit default PUBLIC or PRIVATE declaration is permitted.
• 6601: In a CASE statement, the case-value must be a constant expression.
• 6602: A CYCLE or EXIT statement must not be used with a non-DO block.
• 6603: This construct name has been used more than once in the same nesting level.
• 6604: The CYCLE or EXIT statement must belong to a particular DO construct, and they do not.
• 6605: The required parameter list for a DO construct is missing.
• 6606: The block construct names must match, and they do not.
• 6607: An END SELECT statement exists without an associated SELECT CASE statement.
• 6608: In a CASE statement, the case-expr must be of type INTEGER, CHARACTER, or LOGICAL.
• 6609: A case-selector exists without a preceding SELECT CASE statement.
• 6610: There can be no ranges if the case-expr is of type LOGICAL.
• 6611: The case-value must be of the same type as the case-expr.
• 6612: In a CASE statement, the case-value must be of type INTEGER, CHARACTER, or LOGICAL.
• 6613: This case-value or case-value-range matches a case-value in another case-value-range within the same case-construct.
• 6614: A CASE statement or END SELECT statement must immediately follow this SELECT CASE statement.
• 6615: An unterminated block exists before an END SELECT statement.
• 6616: The next statement cannot be a CONTAINS statement
• 6617: The END statement for a CONTAINed procedure is missing
• 6618: The INTERFACE/CONTAINS stack is full. This means that modules are being 'used' in a circular way.
• 6619: An INTERFACE block is invalid in this context.
• 6620: An END INTERFACE statement exists without a valid INTERFACE statement.
• 6621: This INTERFACE block has not been terminated; an END INTERFACE statement is missing.
• 6622: This statement is invalid in an INTERFACE block.
• 6623: The procedure name of the INTERFACE block conflicts with a name in the encompassing scoping unit.
• 6624: An intrinsic procedure argument that has the INTENT(OUT) attribute must not be an expression or constant.
• 6625: The character lengths of the functions must not be different.
• 6626: The name of the internal procedure conflicts with a name in the encompassing scoping unit.
• 6627: This is an actual argument keyword name, and not a dummy argument name.
• 6628: Non-keyword arguments are invalid after keyword arguments have been encountered.
• 6629: Since the DEFAULT(PRIVATE) is specified for the parallel region, this OpenMP* clause is not permitted on the work-sharing directive.
• 6630: By using keywords, an actual argument has been associated more than once with the same dummy argument.
• 6631: A non-optional actual argument must be present when invoking a procedure with an explicit interface.
• 6632: Keyword arguments are invalid without an explicit interface.
• 6633: The type of the actual argument differs from the type of the dummy argument.
• 6634: The shape matching rules of actual arguments and dummy arguments have been violated.
• 6635: This actual argument must be the name of a procedure and not a data object.
• 6636: This actual argument must be the name of a user subroutine or the name of intrinsic subroutine.
• 6637: This actual argument must be the name of an external user function or the name of an intrinsic function.
• 6638: An actual argument is an expression or constant; this is not valid since the associated dummy argument has the explicit INTENT(OUT) or INTENT(INOUT) attribute.
• 6639: This CONTAINS statement is incorrectly positioned in the scoping unit
• 6640: This input/output keyword is invalid.
• 6641: There are missing arguments in an array reference.
• 6642: There are null arguments in an intrinsic function reference.
• 6643: This statement is incorrectly positioned.
• 6644: The dimension specifications are incompatible.
• 6645: The name of the module procedure conflicts with a name in the encompassing scoping unit.
• 6646: ALLOCATABLE or POINTER attribute dictates a deferred-shape-array
• 6647: The name on a module procedure 'forward' statement conflicts with a name in the encompassing scoping unit
• 6648: This statement is permitted only in an INTERFACE block
• 6649: This symbol has multiple INTENT statement/attribute declarations which is not allowed.
• 6650: This symbol has multiple OPTIONAL statement/attribute declarations which is not allowed.
• 6651: The PROCEDURE specification is allowed only if the interface-block has a generic-spec
• 6652: Attributes must appear only once in a type declaration statement.
• 6653: An alignee must not be a host or use associated object.
• 6654: A distributee must not be a host or use associated entity.
• 6655: The fxx standard requires that the ALLOCATABLE attribute only be given to array objects.
• 6656: module for interface for procedure missing
• 6657: Generating module with interface for procedure.
• 6658: This entity cannot have a PUBLIC/PRIVATE attribute assigned to it.
• 6659: Not an attribute-spec keyword
• 6660: The DATA and PARAMETER attributes must not appear in the same type declaration statement.
• 6661: Unterminated character string within a character format specifier.
• 6662: Module with interface for procedure exists and is up to date.
• 6663: This syntax is invalid; the keywords IN, OUT, or INOUT are required when using the INTENT attribute.
• 6664: Since the processors-name was preceded by '*', this distributee must be a dummy argument of the scoping unit.
• 6665: Since the dist-format-list was preceded by '*', this distributee must be a dummy argument of the scoping unit or have the POINTER attribute.
• 6666: An object-name mentioned as a distributee may not appear as an alignee in an ALIGN or REALIGN directive.
• 6667: An =initialization-expr is missing; an initialization expression is required when using the DATA attribute.
• 6668: A length selector specification is only allowed for CHARACTER type objects.
• 6669: The specification of this object is invalid.
• 6670: This case-value-range defines an empty set of case-values.
• 6671: An ADVANCE= specifier is missing; when a EOR= specifier is present, there must also be an ADVANCE= specifier.
• 6672: This intrinsic procedure or system subprogram must not have an expression or constant as an argument.
• 6673: An ADVANCE= specifier is missing; when a SIZE= specifier is present, there must also be an ADVANCE= specifier.
• 6674: Since a processors-name appears but not a dist-format-list, the rank of the distributee must equal the rank of the named processors arrangement.
• 6675: The number of subscripts in the align-subscript-list for the align-target is different from the number of dimensions for the template/object.
• 6676: Since both a dist-format-list and a processors-name appear, the rank of the processor must equal the number of elements of the dist-format-list that are not '*'.
• 6677: An END TYPE statement exists without an associated TYPE statement.
• 6678: When the target is an expression it must deliver a pointer result.
• 6679: PPD directives shall not appear in the same program unit with OpenMP* directives.
• 6680: A constant is not permitted in this context.
• 6681: This is either an invalid statement, a declaration statement that is ordered incorrectly, or a null procedure statement.
• 6682: This keyword is invalid; if a keyword is used, it must be KIND.
• 6683: A kind type parameter must be a compile-time constant.
• 6684: This is an incorrect value for a kind type parameter in this context.
• 6685: The syntax of the char-selector is invalid.
• 6686: Keyword 'KIND'expected
• 6687: Keyword 'LEN' or 'KIND' expected.
• 6688: The array-spec for a function name with no POINTER attribute must be an explicit shape array (R505.9).
• 6689: An assumed-shape array must be declared as a dummy argument.
• 6690: Too many arguments for a char-selector.
• 6691: A pointer dummy argument may only be argument associated with a pointer.
• 6692: Lower Bound of array is not computable.
• 6693: The array doesn't have a shape.
• 6694: No matching right angle bracket within a character format specifier.
• 6695: The subscript or stride of a FORALL triplet specification must not reference a subscript name.
• 6696: All active combinations of index-names are not used within the variable being defined (i.e., leftside) of this assignment-stmt.
• 6697: The leftside of a forall-assignment is invalid.
• 6698: An index-name is used more than once in a forall-triplet-spec-list.
• 6699: There are too many FORALL triplet specifiers, the FORALL statement has the following syntax: FORALL (triplet_spec [,triplet_spec] ...[,mask-expr]) assignment_stmt.
• 6700: This is invalid; it is not a keyword.
• 6701: The statement associated with the FORALL statement must be a forall-assignment statement.
• 6702: END statement confusion
• 6703: The colon character (:) has been used incorrectly.
• 6704: The same int-name appears on more than one CDEC$ ALIAS directive for the scoping unit
• 6705: The number of arguments for specific procedures sharing the same generic name must be the same. This is a temporary implementation restriction.
• 6706: There is a mixture of specific functions and specific subroutines for one generic-spec.
• 6707: A specific procedure must be a subroutine for a defined ASSIGNMENT
• 6708: A specific procedure must be a function for a defined OPERATOR.
• 6709: The INTENT declaration is incorrect for a defined ASSIGNMENT.
• 6710: The INTENT declaration is incorrect for this dummy argument of the defined operation.
• 6711: The number of function arguments is inconsistent with the intrinsic use of the OPERATOR.
• 6712: The number of subroutines arguments must be 2 in a defined ASSIGNMENT.
• 6713: The function result for a defined OPERATOR must not have assumed character length.
• 6714: There is no visible interface-stmt that defines this generic-spec
• 6715: There are no specific procedures for this generic-spec.
• 6716: This specific procedure has OPTIONAL arguments and is associated with an ASSIGNMENT generic-spec that does not allow OPTIONAL arguments.
• 6717: This name has not been given an explicit type.
• 6718: Distribution attributes improper on scalar objects
• 6719: Copy counts before array constructors (an obsolete F8X feature) are not part of the Fortran Fxx language.
• 6720: The number of arguments for functions for OPERATOR(-) or OPERATOR(+) must be either all 2 or all 1. This is a temporary implementation restriction.
• 6721: This is an invalid specifier; the inquire by output list form of the INQUIRE statement only allows the IOLENGTH= specifier.
• 6722: When using the IOLENGTH= specifier form of the INQUIRE statement, an output list is required.
• 6723: The number of arguments for specific functions for a defined OPERATOR must be the same for all functions.
• 6724: An allocate/deallocate object must have the ALLOCATABLE or POINTER attribute.
• 6725: The scalar integer variable (known as the stat-variable) must not be deallocated with the same DEALLOCATE statement.
• 6726: An explicit-shape-spec in an ALLOCATE statement is incorrect.
• 6727: In an ALLOCATE statement, the stat-variable must not be allocated within the ALLOCATE statement in which it appears.
• 6728: Object must be a variable name or a structure component
• 6729: An allocate-shape-spec-list is required for this allocate object.
• 6730: Not a proper allocate-object for the DEALLOCATE statement
• 6731: Object is not a pointer object
• 6732: Not a proper allocation specifier for the ALLOCATE statement
• 6733: The types of the arguments and the type of the function result must be the same for specific functions associated with defined OPERATORs.
• 6734: The ranks of the arguments and the rank of the function result must be the same for specific functions associated with defined OPERATORs.
• 6735: This specific procedure has OPTIONAL arguments and is associated with an OPERATOR generic-spec that does not allow OPTIONAL arguments.
• 6736: This transformational intrinsic function is invalid in this context; statement functions cannot contain transformational intrinsic functions.
• 6737: The ranks of the arguments must be the same for specific subroutines associated with defined ASSIGNMENTs.
• 6738: The type/rank/keyword signature for this specific procedure matches another specific procedure that shares the same generic-name.
• 6739: Null arguments must not appear in a statement function reference.
• 6740: This edit descriptor is used incorrectly or is invalid.
• 6741: This statement is invalid.
• 6742: This CALL statement is invalid when there are more than zero dummy arguments.
• 6743: The array subscripts are invalid and were encountered when referencing an array.
• 6744: This constant is invalid in this context.
• 6745: The type/rank signature for the arguments of this specific subroutine matches another specific subroutine that shares the same defined ASSIGNMENT.
• 6746: Character types and non-character types must not be mixed in unnamed COMMON blocks.
• 6747: Character types and non-character types must not be mixed in named COMMON blocks.
• 6748: The type/rank for the arguments of this specific function for a defined OPERATOR redefines intrinsic expression operations.
• 6749: The type/rank signature for this specific function and its arguments matches another specific function that shares the same defined OPERATOR.
• 6750: OpenMP* directives shall not appear in the same program unit with PPD directives.
• 6751: A subobject is not permitted as an actual argument when the object has an HPF mapping and there is no explicit interface for the called procedure. Only variable-names, constants, and expressions are permitted.
• 6752: Since the OpenMP* DEFAULT(NONE) clause applies, the PRIVATE, SHARED, REDUCTION, FIRSTPRIVATE, or LASTPRIVATE attribute must be explicitly specified for every variable.
• 6753: The arguments to the SELECTED_INT_KIND and SELECTED_REAL_KIND intrinsic functions must be compile-time constants.
• 6754: An automatic object must not appear in a SAVE statement or be declared with the SAVE attribute.
• 6755: A COMMON block data object may not have the SAVE attribute.
• 6756: A COMMON block data object must not be an automatic object.
• 6757: This entity has already been privatized in the parallel region and cannot be privatized again by this OpenMP* work-sharing directive.
• 6758: This name is invalid; if a name is present, it must match the corresponding interface body name.
• 6759: A COMMON block data object must not have the ALLOCATABLE attribute.
• 6760: An equivalenced data object must not be an automatic object.
• 6761: An entity cannot appear explicitly in more than one clause per directive except that an entity can be specified in both a FIRSTPRIVATE and LASTPRIVATE clause.
• 6762: The type for the arguments of this specific subroutine for a defined ASSIGNMENT redefines intrinsic assignment operations.
• 6763: An equivalenced data object must not have the ALLOCATABLE or POINTER attribute.
• 6764: A unary defined OPERATOR definition is missing or incorrect.
• 6765: An OpenMP* SINGLE directive is not permitted in a SECTIONS directive that binds to the same PARALLEL directive.
• 6766: A binary defined OPERATOR definition is missing or incorrect.
• 6767: No matching user defined OPERATOR with the given type and rank has been defined.
• 6768: A logical type specific function result is required for extending relational OPERATORs.
• 6769: aeACvalueListElement
• 6770: This TRANSFER transformational intrinsic function is not [yet] supported in initialization expressions.
• 6771: The stride must not be zero; it can be negative or positive but it cannot be zero.
• 6772: A PARAMETER must not be defined in terms of itself.
• 6773: An equals sign (=) is invalid in this context.
• 6774: A substring of length zero is being referenced.
• 6775: The size of SOURCE must be greater than or equal to PRODUCT(SHAPE).
• 6776: An array dimension is of size zero.
• 6777: An OpenMP* SINGLE directive is not permitted in a DO directive that binds to the same PARALLEL directive.
• 6778: An implicit CHARACTER data type of length zero is defined.
• 6779: An OpenMP* DO directive is not permitted in a SINGLE directive that binds to the same PARALLEL directive.
• 6780: A dummy argument with the INTENT(IN) attribute shall not be defined nor become undefined.
• 6781: The number of INDX arguments does not equal the rank of BASE.
• 6782: BASE must be of the same typo and kind type parameter as ARRAY.
• 6783: The variable being defined does not conform with the mask-expr of the where-construct or where-stmt.
• 6784: The number of actual arguments cannot be greater than the number of dummy arguments.
• 6785: This name does not match the unit name.
• 6786: This is an invalid statement; an END [MODULE] statement is required.
• 6787: This is an invalid statement; an END [FUNCTION] statement is required.
• 6788: This is an invalid statement; an END [SUBROUTINE] statement is required.
• 6789: This is an invalid statement; an END [BLOCK DATA] statement is required.
• 6790: This is an invalid statement; an END [PROGRAM] statement is required.
• 6791: The int-name on a CDEC$ ALIAS directive cannot apply to a host associated symbol; i.e., the directive must be placed in the same scoping unit as int-name.
• 6792: The rank of the allocate-shape-spec-list differs from the rank of the allocate-object.
• 6793: The POINTER attribute is required
• 6794: The rank of the target is different from the pointer
• 6795: The target must be of the same type and kind type parameters as the pointer.
• 6796: The variable must have the TARGET attribute or be a subobject of an object with the TARGET attribute, or it must have the POINTER attribute.
• 6797: A vector subscript is not permitted in an array section target subobject
• 6798: The keyword STAT is required to specify a scalar integer variable within an ALLOCATE statement.
• 6799: An OpenMP* DO directive is not permitted in a SECTIONS directive that binds to the same PARALLEL directive.
• 6800: If the first argument of this intrinsic function is of type COMPLEX, the second argument must not be present.
• 6801: A dummy argument is required in this context.
• 6802: The argument to the PRESENT intrinsic function shall be the name of an optional dummy argument of the procedure in which the PRESENT function reference appears.
• 6803: The type/rank for this specific procedure is the same as the associated intrinsic procedure or another specific procedure
• 6804: The POINTER argument must have the POINTER attribute.
• 6805: If the first argument of an intrinsic function is an assumed-size array, the second argument must be present.
• 6806: The number of RANDOM_SEED arguments is incorrect; the RANDOM_SEED intrinsic subroutine must have exactly 0 or 1 arguments.
• 6807: Invalid VFE.
• 6808: The TARGET argument must have the POINTER or TARGET attribute.
• 6809: The COMPLEX data type is not valid in this context.
• 6810: The dimensions of an object must be known at compile time. The DIM= argument requires an integer constant expression.
• 6811: The SEQUENCE statement is incorrectly positioned within the derived-type definition.
• 6812: The size of this object cannot be evaluated to a constant.
• 6813: When using this inquiry function, the bounds of this object cannot be evaluated to a constant.
• 6814: When using this inquiry function, the length of this object cannot be evaluated to a constant.
• 6815: Vector-valued constant expressions are not supported.
• 6816: When using this inquiry function, the shape of this object cannot be evaluated to a constant.
• 6817: The PRIVATE statement is incorrectly positioned within the derived-type definition.
• 6818: The statement following a CONTAINS is not a function-stmt or a subroutine-stmt.
• 6819: This entry point does not define all dummy variables used in bounds or length expressions of other dummy objects in its dummy argument list.
• 6820: An OpenMP* SECTIONS directive is not permitted in a SINGLE directive that binds to the same PARALLEL directive.
• 6821: A scalar constant is required in this context.
• 6822: An array variable is valid in this context, but an array section or array expression is not valid.
• 6823: This entry point does not define all dummy variables used in bounds or length expressions of automatic data objects.
• 6824: This dummy variable is used in bounds or length expressions of automatic data objects but is not defined at all entry points of the scoping unit.
• 6825: For array constructors, the implied do expression must reduce to a constant.
• 6826: A NAMELIST group object must not be an array with nonconstant bounds.
• 6827: A NAMELIST item must not be a dummy argument.
• 6828: A function result is not valid in this context.
• 6829: This constant is invalid in this context.
• 6830: The argument of the ALLOCATED intrinsic cannot be a constant or an expression.
• 6831: The result-name in the construct 'RESULT(result-name)' may only be used once; it incorrectly appears elsewhere in specification statements.
• 6832: This passed length character name has been used in an invalid context.
• 6833: The RESULT data type is multiply specified: on function statement and result name.
• 6834: Array specifications must be given for result name, not function.
• 6835: Recursive array-valued function without result variable ambiguous
• 6836: Function name must not appear in any specification statement when result name specified
• 6837: The leftmost part-ref in a data-ref can not be a function reference.
• 6838: An object must not have both the POINTER and the TARGET attribute.
• 6839: An OpenMP* SECTIONS directive is not permitted in a DO directive that binds to the same PARALLEL directive.
• 6840: In a DO loop associated with a PPD PARALLEL DO or PDO directive, the iteration variable must be of an integer type.
• 6841: An automatic object must not appear in the specification part of a module.
• 6842: In a DO loop associated with an OpenMP* PARALLEL DO or DO directive, the iteration variable must be of an integer type.
• 6843: A dummy argument with an explicit INTENT(OUT) declaration is not given an explicit value.
• 6844: A subprogram kind may not appear on an END statement.
• 6845: A construct name is not allowed in this context.
• 6846: A subprogram name may not appear on an END statement.
• 6847: This statement is valid only in the specification part of a module.
• 6848: This attribute specification is valid only in the specification part of a module.
• 6849: This attribute specification is not valid in a BLOCK DATA program unit.
• 6850: This attribute specification is not valid in the main scoping unit.
• 6851: LOGICAL(KIND=1) (also known as the BYTE type) is not valid.
• 6852: LOGICAL(KIND=2) (2 Byte LOGICAL type) is not valid.
• 6853: LOGICAL(KIND=4) (4 Byte LOGICAL type) is not valid.
• 6854: Until supported, INTEGER(KIND=8) is equivalent to INTEGER(KIND=4).
• 6855: Until supported, INTEGER(KIND=1) is equivalent to INTEGER(KIND=2).
• 6856: INTEGER(KIND=2) (2 Byte INTEGER type) is not valid.
• 6857: INTEGER(KIND=4) (4 Byte INTEGER type) is not valid.
• 6858: REAL(KIND=4) (4 Byte REAL type) is not valid.
• 6859: REAL(KIND=8) (8 Byte REAL type) is not valid.
• 6860: REAL(KIND=16) (16 Byte REAL type) is not valid.
• 6861: COMPLEX(KIND=4) (8 Byte COMPLEX type) is not valid.
• 6862: COMPLEX(KIND=8) (16 Byte COMPLEX type) is not valid.
• 6863: The CHARACTER data type is not valid.
• 6864: Until supported, LOGICAL(KIND=8) is equivalent to LOGICAL(KIND=4).
• 6865: This is not a valid data type.
• 6866: Dotted string neither a defined operator nor a structure component
• 6867: This ENDDO statement requires a label.
• 6868: The label on this ENDDO statement is incorrect.
• 6869: An extra DO construct label was incorrectly referenced.
• 6870: An extra DO construct label was incorrectly referenced.
• 6871: There is an extra DO construct label.
• 6872: A subscript is out-of-range.
• 6873: The run-time format specifier must be of type CHARACTER.
• 6874: When converting this constant to a REAL(KIND=4) number, underflow or overflow occurred.
• 6875: The syntax of the WRITE statement is not valid.
• 6876: An END= specifier is not valid in a direct access READ statement.
• 6877: rrSFUNCexpand
• 6878: Within an interface block, this statement is ignored.
• 6879: An expression cannot be used as part of the format list.
• 6880: The syntax is incorrect, an E or D for exponentiation or a delimiter was expected.
• 6881: A FORMAT statement maximum has been exceeded. The current limit for the format specification is 2048.
• 6882: In this context, the external procedure name is not valid.
• 6883: A constant was expected as part of the format list.
• 6884: The format groups are nested too deeply within the format list.
• 6885: A dangling constant exists.
• 6886: Dangling
• 6887: External functions with explicit interface are not supported in statement functions
• 6888: Result name is given. May not use entry-name as variable
• 6889: Function name may not be used in this context. Should use result-name
• 6890: Scalar or vector (1 dimension) argument expected
• 6891: In a format list, the character following the P edit descriptor is not standard Fortran xx.
• 6892: adSameSymAttributes
• 6893: In a format list, the required delimiter is missing. This is an extension to Standard Fxx.
• 6894: The field width is too small for the number of fractional digits.
• 6895: The subroutine/function has already been defined within an INTERFACE statement.
• 6896: The number of dummy arguments in the subroutine/function differs from the number of arguments to the same subroutine/function that are redefined within the INTERFACE statement.
• 6897: An interface-block in a subprogram must not contain an interface-body for a procedure defined by that subprogram.
• 6898: Too many characters in a character string within a CHARACTER format specifier.
• 6899: First non-blank character in a character type format specifier must be a left parenthesis.
• 6900: More than 1 Hollerith character is being stored in this CHARACTER variable.
• 6901: The decimal constant was too large when converting to an integer, and overflow occurred.
• 6902: This syntax is invalid; a label was expected.
• 6903: The octal constant was too large when converting to an integer, and will be truncated on the left side.
• 6904: This label has too many digits; a label has a maximum of a 4 digit integer.
• 6905: A label cannot be zero; it must be an integer in the range 1 through 99999.
• 6906: The value of the integer is either too great or too small, and overflow/underflow occurred.
• 6907: Dividing an integer by zero is mathematically illegal.
• 6908: A hexadecimal character must be in the range 0 through 9 or in the range A through F.
• 6909: An octal digit must be in the range 0 through 7.
• 6910: An INTEGER data type is required in this context.
• 6911: The syntax of this substring is invalid.
• 6912: The hexadecimal constant is too long for the largest numeric type.
• 6913: The octal constant is too long for the largest numeric type.
• 6914: The Hollerith constant was too large when converting to an integer, and will be truncated on the right side.
• 6915: Fortran xx does not allow data values on a type statement.
• 6916: Fortran xx does not allow this length specification.
• 6917: This array with adjustable declarators must be declared a dummy argument.
• 6918: Unless you are using the NOF77 switch, the Fortran 66 convention of using an asterisk to specify a function for an EXTERNAL statement is not valid.
• 6919: Fortran xx does not allow the type-specifier on this statement.
• 6920: In this context, Fortran xx does not allow a single subscript in an EQUIVALENCE statement.
• 6921: Fortran xx does not accept UNIT and RECORD specifiers in the form UNIT'RECORD for direct access I/O.
• 6922: Fortran xx does not allow character types and non-character types to be mixed in named COMMON blocks.
• 6923: Fortran xx does not allow an expression to be used as part of the format list.
• 6924: Fortran xx does not allow this constant.
• 6925: Fortran xx does not allow character types and non-character types to be mixed in unnamed COMMON blocks.
• 6926: The function result of this module procedure is of a type that has PRIVATE accessibility and has a generic identifier that has PUBLIC accessibility, this is not allowed by Fortran Fxx.
• 6927: This dummy argument of this module procedure is of a type that has PRIVATE accessibility and the procedure has a generic identifier that has PUBLIC accessibility, this is not allowed by Fortran Fxx.
• 6928: The module-name on a USE statement in a program unit cannot be the name of any encompassing scoping unit.
• 6929: An object-name mentioned as a distributee must be a simple name and not a subobject designator.
• 6930: The size of the array dimension is too large, and overflow occurred when computing the array size.
• 6931: Fortran xx does not allow this assignment statement.
• 6932: An OpenMP* PARALLEL SECTIONS directive is not permitted in the dynamic extent of a CRITICAL, MASTER, or ORDERED directive.
• 6933: In this context, Fortran xx does not allow a symbol token to be defined as a parameter.
• 6934: The function and entry names do not have consistent data types. They do not have to be the same data type, but they must be in the same data type group.
• 6935: Overflow occurred when computing the displacement from the base of the array for an array reference.
• 6936: In this context, exponentiation for constant expressions of type complex is not valid.
• 6937: The value was either too large or too small when converting to a REAL(KIND=8) number, and overflow/underflow occurred.
• 6938: The length of the character constant is out-of-range.
• 6939: The constant cannot be evaluated because the parameter definition is faulty.
• 6940: The value of a REAL(KIND=4) constant is either too great or too small, and overflow/underflow occurred.
• 6941: When dividing, the absolute value of a complex constant cannot be zero.
• 6942: Dividing a real number by zero is mathematically illegal.
• 6943: The character length specifier must be a compile time constant in Fortran xx standard.
• 6944: An OpenMP* PARALLEL DO directive is not permitted in the dynamic extent of a CRITICAL, MASTER or ORDERED directive.
• 6945: Fortran xx does not allow a negative number of iterations in an implied DO loop.
• 6946: In this DATA statement, there are more values assigned to variables then there are variables. There must be the same number of values and variables.
• 6947: An object may not have both the INHERIT attribute and the ALIGN attribute
• 6948: The same combined-attribute must not appear more than once in a given combine-directive
• 6949: Object with DIMENSION attribute in a combined directive must have TEMPLATE or PROCESSORS type specifier
• 6950: The first non-comment line following an independent-directive with NEW or REDUCTION option must be a do-stmt
• 6951: The first non-comment line following an independent-directive must be a do-stmt, forall-stmt, or a forall-construct
• 6952: Numeric data cannot be stored into a variable of type CHARACTER.
• 6953: Fortran xx does not allow an 8-bit integer ASCII constant to be stored in a CHARACTER constant.
• 6954: The result variable of an array-valued function may not appear in a SEQUENCE directive
• 6955: Blank common may appear at most once in a sequence-directive within any scoping unit
• 6956: In this DATA statement, there are more variables than values assigned to the variables.
• 6957: This is an illegal data type value for this parameter.
• 6958: No explicit mapping may be given for a component of a derived type having the SEQUENCE attribute
• 6959: The array constructor must be a constant.
• 6960: This form of array initialization is not currently supported
• 6961: In this context, the length of an array constructor on a DATA statement cannot be zero.
• 6962: The scalar-integer-expression that specifies the number of consecutive copies of the associated array constructor must not be negative.
• 6963: The array constructors are nested too deeply.
• 6964: This is an illegal octal, hexadecimal, or binary character; or, the value of the constant is too large or too small.
• 6965: A variable in the NEW or REDUCTION clause of the INDEPENDENT directive may not have the SAVE attribute
• 6966: A variable in the NEW or REDUCTION clause of the INDEPENDENT directive may not have the TARGET attribute
• 6967: A variable in the NEW or REDUCTION clause of the INDEPENDENT directive must not be a dummy argument
• 6968: A variable in the NEW or REDUCTION clause of the INDEPENDENT directive may not be associated with another object as a result of appearing in an EQUIVALENCE statement
• 6969: A sequential object may not be explicitly mapped.
• 6970: An object-name mentioned as an alignee may not appear as a distributee on a DISTRIBUTE or REDISTRIBUTE directive.
• 6971: An OpenMP* ORDERED directive is not permitted in the dynamic extent of the CRITICAL directive.
• 6972: Since the align-spec was preceded by '*', this alignee must be a dummy argument of the scoping unit or have the POINTER attribute.
• 6973: This is not a valid initialization expression.
• 6974: This is not a valid statement.
• 6975: A kind-param must be a digit-string or a scalar-int-constant-name
• 6976: There are multiple INHERIT directives in a single scoping unit.
• 6977: ONTO must be followed by '*', identifier, or *identifier.
• 6978: A transcriptive dist-target (i.e., 'ONTO *') is not [yet] supported.
• 6979: A dummy assumed-shape array or the POINTER attribute is required for names on the INHERIT directive.
• 6980: Since no 64 bit word, LOGICAL(KIND=8) will be treated the same as LOGICAL(KIND=4).
• 6981: Since no 64 bit word, INTEGER(KIND=8) will be treated the same as INTEGER(KIND=4).
• 6982: An object in COMMON may not be declared DYNAMIC.
• 6983: The array dimension has a size of zero.
• 6984: A scalar constant exists where an array constructor is required.
• 6985: An object with the SAVE attribute may not be declared DYNAMIC.
• 6986: There are multiple DYNAMIC directives in a single scoping unit.
• 6987: The increment in the implied-do loop is zero.
• 6988: In this context, the implied-do variable is not valid.
• 6989: An object in COMMON may not be aligned to an object or template that is DYNAMIC.
• 6990: An object with the SAVE attribute may not be aligned to an object or template that is DYNAMIC.
• 6991: A variable or COMMON block name may appear at most once in a sequence directive in a scoping unit.
• 6992: The keyword 'HPF', 'HPF_LOCAL', or 'HPF_SERIAL' is expected.
• 6993: An EXTRINSIC(HPF_LOCAL) procedure cannot be recursive.
• 6994: An EXTRINSIC(HPF_LOCAL) procedure may not have a dummy procedure argument.
• 6995: An EXTRINSIC(HPF_LOCAL) procedure may not have alternate returns.
• 6996: An EXTRINSIC(HPF_LOCAL) procedure cannot have a dummy POINTER argument.
• 6997: There are multiple extrinsic-prefixes in a single scoping unit.
• 6998: The explicit EXTRINSIC(...) prefix for this internal procedure does not agree with the parent procedure.
• 6999: An extrinsic-prefix can appear in only a SUBROUTINE or FUNCTION scoping unit.

Back to All Intel Fortran Compiler Diagnostics

• 7000: Two-digit year return value may cause problems with the year 2000. Use DATE_AND_TIME instead
• 7001: Error in creating the compiled module file.
• 7002: Error in opening the compiled module file. Check INCLUDE paths.
• 7003: Error in closing the compiled module file.
• 7004: Error in writing the compiled module file.
• 7005: Error in reading the compiled module file.
• 7006: Nothing was exported from this module.
• 7007: ** NYI ** Exporting this declaration is currently nyi.
• 7008: Invalid structure component
• 7009: Attribute syntax is not standard Fxx
• 7010: Due to file table overflow, the module file cannot be opened. Too many files are open.
• 7011: The module file for the module is obsolete. Please recompile the module.
• 7012: The module file cannot be read. Its format requires a more recent Fxx compiler.
• 7013: This module file was not generated by any release of this compiler.
• 7014: Cannot initialize a '%FILL' structure field
• 7015: Multiple PROCESSORS attribute
• 7016: Multiple TEMPLATE attribute
• 7017: Multiple ALIGN attribute
• 7018: Multiple DISTRIBUTE attribute
• 7019: Multiple INHERIT attribute
• 7020: Multiple DYNAMIC attribute
• 7021: Name invalid in this context
• 7022: Improper type definition for initializing structure variable
• 7023: Fortran xx does not allow radix-specified constants
• 7024: Invalid radix or character in constant out of radix range
• 7025: This directive is not standard Fxx.
• 7026: Non-standard extension
• 7027: Vax Structure/derived type equivalence is invalid in Fortran xx standard
• 7028: Integer pointer non-standard
• 7029: Invalid context for NULL(...).
• 7030: The type of the NULL(MOLD) element in a structure-constructor differs from the type of the component in the derived-type-def.
• 7031: END STRUCTURE without a STRUCTURE; expected END UNION.
• 7032: END STRUCTURE without a STRUCTURE; expected END MAP.
• 7033: END UNION without a UNION; expected END STRUCTURE.
• 7034: END UNION without a UNION; expected END MAP.
• 7035: END MAP without a MAP; expected END STRUCTURE.
• 7036: END MAP without a MAP; expected END UNION.
• 7037: A field cannot be of a STRUCTURE type that is part of the current definition.
• 7038: A nested structure declaration must have at least one field name in the field list.
• 7039: Keyword 'SHADOW', 'LOW_SHADOW', 'HIGH_SHADOW', or 'BLOCKSIZE' is expected.
• 7040: The dist-format is incorrect.
• 7041: A shadow-spec cannot appear in a CYCLIC dist-format unless a blocksize-spec appears.
• 7042: Scalar integer initialization-expression is required for the int-expr part of a shadow-spec.
• 7043: Cannot have non-keyword direction after keyword direction has been used.
• 7044: The blocksize-spec appears more than once in a dist-format.
• 7045: Conflicting or multiply occurring shadow-specs in a dist-format.
• 7046: The rank of the NULL(MOLD) element in a structure-constructor differs from the rank of the component in the derived-type-def.
• 7047: A NULL(MOLD), i.e., an explicit mold is not permitted in this context.
• 7048: In Fortran 90, the obsolescent Hollerith constant is not permitted in this context.
• 7049: The Hollerith constant has been deleted from Fortran xx.
• 7050: The PURE attribute of the associated actual procedure differs from the PURE attribute of the dummy procedure.
• 7051: A do-construct is incorrectly nested.
• 7052: REAL(KIND=16) is not supported on this platform.
• 7053: An OpenMP* BARRIER directive is not permitted in the dynamic extent of a DO, PARALLEL DO, SECTIONS, PARALLEL SECTIONS, SINGLE, CRITICAL, ORDERED, or TASK directive.
• 7054: This specific procedure is a subroutine and the generic_name is an intrinsic function.
• 7055: This specific procedure is a function and the generic_name is an intrinsic subroutine.
• 7056: Allowing integer arguments to be logical for this intrinsic function is not standard Fortran xx
• 7057: DATA is an obsolescent type-declaration-stmt attribute and may not be supported in future releases; the fxx standard requires no attribute declaration.
• 7058: This SIZEOF function call cannot appear in an initialization expression.
• 7059: ARRAY is an obsolescent type-declaration-stmt attribute and may not be supported in future releases; use the fxx standard DIMENSION attribute.
• 7060: This intrinsic function is permitted only within a function or subroutine subprogram.
• 7061: The characteristics of dummy argument 1 of the associated actual procedure differ from the characteristics of dummy argument 1 of the dummy procedure. (12.2)
• 7062: The characteristics of dummy argument 2 of the associated actual procedure differ from the characteristics of dummy argument 2 of the dummy procedure. (12.2)
• 7063: The characteristics of dummy argument 3 of the associated actual procedure differ from the characteristics of dummy argument 3 of the dummy procedure. (12.2)
• 7064: The characteristics of dummy argument 4 of the associated actual procedure differ from the characteristics of dummy argument 4 of the dummy procedure. (12.2)
• 7065: The characteristics of dummy argument 5 of the associated actual procedure differ from the characteristics of dummy argument 5 of the dummy procedure. (12.2)
• 7066: The characteristics of dummy argument 6 of the associated actual procedure differ from the characteristics of dummy argument 6 of the dummy procedure. (12.2)
• 7067: The characteristics of dummy argument 7 of the associated actual procedure differ from the characteristics of dummy argument 7 of the dummy procedure. (12.2)
• 7068: The characteristics of a dummy argument of the associated actual procedure differ from the characteristics of the same dummy argument of the dummy procedure. (12.2)
• 7069: The characteristics of the associated actual function result differ from the characteristics of the dummy function result. (12.4.1.2, 12.2.2)
• 7070: The number of arguments of the associated actual procedure is different from the number of arguments of the dummy procedure.
• 7071: The classification of the associated actual procedure differs from the classification of the dummy procedure; i.e., one is subroutine and one is function.
• 7072: For the given arguments, this intrinsic function is undefined.
• 7073: The type of the argument[s] of this intrinsic procedure in an initialization expression must be integer.
• 7074: Out-of-range value.
• 7075: The actual argument has no distribution and the dummy argument has descriptive directives.
• 7076: Because the actual arg is a section and because there is no alignment, the descriptive distribution of the dummy arg may not accurately describe the mapping of the actual arg.
• 7077: An explicit-shape-spec is required in this context.
• 7078: EXTRINSIC(SCALAR) is an obsolescent extrinsic-prefix and may not be supported in future releases; use the equivalent EXTRINSIC(HPF_SERIAL).
• 7079: Mapping directives for arrays appearing in the specification part of a module will be ignored because the array has a data initializer.
• 7080: All active combinations of index-name values are not used within the target of a pointer-assignment-stmt in a forall-assignment.
• 7081: All active combinations of index-name values are not used within the pointer-object (i.e., the leftside) of a pointer-assignment-stmt in a forall-assignment.
• 7082: All active combination of index-name values are not used within the leftside of this assignment-stmt.
• 7083: The pointer-assignment-stmt is not [yet] supported as a forall-assignment statement.
• 7084: Mapping directives for arrays appearing in the specification part of a module will be ignored because the number of nodes is not specified at compile time
• 7085: This index-name redefines an index-name used in an outer forall-construct.
• 7086: This statement in a FORALL construct is invalid.
• 7087: The where-stmt or the where-construct is not [yet] supported as a forall-body-stmt.
• 7088: The FORALL stack has been exceeded. The current limit is 7.
• 7089: The INDEPENDENT directive is checked for syntactic and semantic correctness, but it is then ignored by the current HPF compiler.
• 7090: The DYNAMIC directive is checked for syntactic and semantic correctness, but it is then ignored by the current HPF compiler.
• 7091: Error in writing the Fuse cross-reference file
• 7092: No more memory while writing the Fuse cross-reference file
• 7094: Unmatched parentheses within a character format specifier.
• 7095: A dummy argument of type REAL(KIND=16) can not have the VALUE attribute.
• 7096: The type/rank/keyword signature for this specific procedure matches another specific procedure that shares the same generic-spec.
• 7097: The type of the argument[s] of this intrinsic procedure in an initialization expression must be real.
• 7098: A dummy argument object cannot be a pointee.
• 7099: The second argument must be of the same type and type parameters as the first argument.
• 7100: The third argument must be of the same type and type parameters as the first argument.
• 7101: An ENTRY statement must not appear within an executable construct (R1223.2).
• 7102: An OpenMP* MASTER directive is not permitted in the dynamic extent of a DO, PARALLEL DO, SECTIONS, PARALLEL SECTIONS, or SINGLE directive.
• 7103: A where-assignment-stmt that is a defined assignment shall be elemental.
• 7104: A statement entity having the same name as a constant in the same scoping unit is not standard Fortran xx.
• 7105: The name of a statement entity must not be the same name as a derived type.
• 7106: The name of a statement entity must not be the same name as an external function or subroutine.
• 7107: This type conflicts with a previous implicit typing of a statement function dummy with the same name.
• 7108: A dummy argument is not used in the statement function expression.
• 7109: A binary digit must be in the range 0 through 1.
• 7110: The binary constant is too long for the largest numeric type.
• 7111: An interface-body is incorrectly positioned within a program unit.
• 7112: This actual argument must not be the name of a procedure.
• 7113: Each ac-value expression in an array-constructor must have the same type and type parameters.
• 7114: All ac-values in an array constructor of type CHARACTER are not the same length.
• 7115: The specification-part of a PURE function must specify that all dummy arguments have explicitly declared INTENT(IN) except procedure arguments and arguments with the POINTER attribute.
• 7116: All ac-values in this array constructor of type CHARACTER are not the required length.
• 7117: The argument must be of the same type and type parameters as its predecessor model argument.
• 7118: The argument must be of the same type and type parameters as the first argument.
• 7119: Any function referenced in a forall-body-stmt must have the PURE attribute explicitly declared.
• 7120: The lo:high[:stride] array constructor syntax is not standard Fortran xx.
• 7121: A ptr dummy may only be argument associated with a ptr, and this array element or section does not inherit the POINTER attr from its parent array.
• 7122: Distribution attributes improper on assumed size arrays.
• 7123: In Fortran xx, the case-value must be of the same type and kind type parameter as the case-expr.
• 7124: The dummy procedure characteristics do not match.
• 7125: Since the number of processors is not a compile time constant, this intrinsic function is invalid in constant expressions.
• 7126: This storage associated function-name or entry-name must not have the POINTER attribute.
• 7127: The characteristics of the function named on the ENTRY statement are different from the characteristics of the result of the function named on the FUNCTION statement.
• 7128: A derived-type-def must have at least one component-def-stmt.
• 7129: The case-value is out-of-range.
• 7130: The 'TO' argument must not be a scalar if other arguments of MVBITS are arrays.
• 7131: The permutation specified in the ORDER argument is invalid.
• 7132: The shape specified in the SHAPE argument is invalid.
• 7133: A PURE procedure must not contain a stop-stmt, errorstop-stmt or pause-stmt
• 7134: A PURE procedure must not contain a print-stmt, open-stmt, close-stmt, backspace-stmt, endfile-stmt, rewind-stmt, inquire-stmt
• 7135: A PURE procedure must not contain a read-stmt or write-stmt whose io-unit is an external-file-unit or *
• 7136: A PURE procedure must not contain this statement.
• 7137: Any procedure referenced in a PURE procedure, including one referenced via a defined operation or assignment, must have an explicit interface and be declared PURE.
• 7138: This dummy-arg appears in a 'defining' context in a PURE procedure or in an internal procedure contained in a PURE procedure.
• 7139: This global common-block-object, or object storage associated with a global common-block-object, appears in a 'defining' context in a PURE procedure or in an internal procedure contained in a PURE procedure.
• 7140: This global use associated object appears in a 'defining' context in a PURE procedure or in an internal procedure contained in a PURE procedure.
• 7141: Initialization of this object is not permitted in a PURE procedure or an internal procedure contained in a PURE procedure.
• 7142: A data-stmt-object must not be a dummy argument
• 7143: This object has the SAVE attribute but must not have the SAVE attribute in a PURE procedure or an internal procedure contained in a PURE procedure.
• 7144: This object has the DYNAMIC attribute but must not have the DYNAMIC attribute in a PURE procedure or an internal procedure contained in a PURE procedure.
• 7145: This object must not be used as the pointer-object or target of a pointer-assignment-stmt in a PURE procedure or an internal procedure contained in a PURE procedure.
• 7146: This object must not be used as an allocate-object in an allocate-stmt or deallocate-stmt in a PURE procedure or an internal procedure contained in a PURE procedure.
• 7147: This object must not be used as a pointer-object in a nullify-stmt in a PURE procedure or an internal procedure contained in a PURE procedure.
• 7148: Arguments incompatible with intrinsic procedure, assume EXTERNAL.
• 7149: An automatic object is invalid in a BLOCK DATA unit.
• 7150: Explicit-shape-specs in a TEMPLATE directive must be constant expressions in a BLOCK DATA unit.
• 7151: The explicit-shape-specs in a TEMPLATE directive are invalid for the specification-part of a MODULE.
• 7152: The explicit-shape-specs in a TEMPLATE directive are invalid for a main program.
• 7153: Explicit-shape-specs in a PROCESSORS directive must be constant expressions in a BLOCK DATA unit.
• 7154: The explicit-shape-specs in a PROCESSORS directive are invalid for the specification-part of a MODULE.
• 7155: The explicit-shape-specs in a PROCESSORS directive are invalid for a main program.
• 7156: A transcriptive dist-format-clause (i.e., a standalone '*') is not (yet) supported.
• 7157: This name has been incorrectly used in a specification expression of a contained procedure.
• 7158: Array attributes for this symbol occurred after the data initializers.
• 7159: Array declarations for a symbol appearing after the DATA statement is not permitted in standard Fortran xx.
• 7160: For an elemental procedure, the actual arg supplied is an array which is itself optional, and there are no arrays supplied for the nonoptional positions.
• 7161: There are unresolved generics appearing in ONLY clauses for this external module.
• 7162: If an equiv-object is of type default integer, default real, double precision, default complex, default logical, or numeric sequence type, all of the objects in the equiv set must be of these types.
• 7163: If an equivalence-object is of type default character or character sequence type, all of the objects in the equivalence set must be of these types.
• 7164: If an equiv-object is of a derived type that is not a numeric sequence or character sequence type, all of the objects in the equiv set must be of the same type.
• 7165: If an equiv-object is of type other than default integer, real, double precision, complex, logical, or character, all of the objects in the equiv set must be of the same type with the same kind type parameter value.
• 7166: This is not a proper equivalence-object.
• 7167: The PURE prefix-spec is not standard Fortran xx
• 7168: The EXTRINSIC prefix-spec is not standard Fortran xx
• 7169: Bad initialization expression.
• 7170: The POINTER attribute is not permitted for a do-variable.
• 7171: A data initialization-expr is not valid on a component-def-stmt.
• 7172: The distribution from the actual argument is incorrect for the descriptive distribution of the dummy argument.
• 7173: The PARAMETER attribute must not be specified for a deferred-shape array.
• 7174: The AUTOMATIC attribute is not allowed with a function result.
• 7175: This object has already been specified AUTOMATIC.
• 7176: This object has already been specified STATIC.
• 7177: The AUTOMATIC attribute is not allowed with the SAVE or STATIC attributes.
• 7178: An equivalenced data object must not be specified AUTOMATIC.
• 7179: An automatic object must not appear in a STATIC statement or be declared with the STATIC attribute.
• 7180: An OpenMP* SINGLE directive is not permitted in the dynamic extent of a CRITICAL, MASTER or ORDERED directive.
• 7181: The STATIC attribute is not allowed with a function result.
• 7182: A COMMON block data object must not have the AUTOMATIC attribute.
• 7183: An object with the AUTOMATIC attribute must not appear in the specification part of a module.
• 7184: An interface-block in a subprogram that contains an interface-body for a procedure defined by that subprogram is not standard Fxx.
• 7185: A dummy argument of a pure subroutine may not be explicitly distributed or given the INHERIT attribute.
• 7186: A dummy argument of a pure subroutine may be explicitly aligned only with another dummy argument.
• 7187: In a pure subroutine, a local variable may be explicitly aligned only with another local variable or a dummy argument.
• 7188: In a pure procedure, a local variable may not be explicitly distributed.
• 7189: The value was either too large or too small when converting to a REAL(KIND=16) number, and overflow/underflow occurred.
• 7190: An HPF global procedure must not be called from within an HPF local procedure.
• 7191: An intrinsic operation or function causes REAL(KIND=8) overflow/underflow/
• 7192: An intrinsic operation or function causes REAL(KIND=4) overflow/underflow/
• 7193: The alignment for this object is circular.
• 7194: This object must not be aligned with an unallocated object.
• 7195: A dummy argument or the dummy result of a pure function may not be explicitly distributed or given the INHERIT attribute.
• 7196: A dummy argument or the dummy result of a pure function may be explicitly aligned only with another dummy argument or the dummy result.
• 7197: In a pure function, a local variable may be explicitly aligned only with another local variable, a dummy argument, or the result variable.
• 7198: Indexed IO is a VMS only feature.
• 7199: Unsupported qualifier or qualifier value in OPTIONS statement.
• 7200: Ambiguous OPTIONS statement qualifier or qualifier value.
• 7201: An external procedure name or a passed-by-value INTEGER(KIND=4) or INTEGER(KIND=8) expression is required.
• 7202: This OPTIONS statement qualifier or qualifier value is not supported on this platform.
• 7203: An ac-value-list of an array-constructor must contain at least one ac-value
• 7204: The alignment or distribution specification for this object is dependent on an object that depends on this object.
• 7205: This object is dependent on an object whose distribution/alignment specification is dependent on this object.
• 7208: Non-existent or incorrectly used OPTIONS directive keyword.
• 7209: Ambiguous OPTIONS directive keyword.
• 7210: A 'COMMONS', 'RECORDS', or 'STRUCTURES' keyword is expected.
• 7211: An 'ALIGN', 'NOALIGN', 'WARNINGS', 'NOWARNINGS', or 'OFFLOAD_ATTRIBUTE_TARGET' keyword is expected.
• 7212: The 'STANDARD' keyword is invalid in this context.
• 7213: The 'ALL' or 'NONE' keyword is invalid in this context.
• 7214: Multiple CDEC$ PSECT directives for common block for this scoping unit; the PSECTs attributes will be merged with the last taking precedence.
• 7215: A CDEC$ OPTIONS directive exists without an associated CDEC$ END OPTIONS directive.
• 7216: A CDEC$ ENDOPTIONS directive occurred without a corresponding CDEC$ OPTIONS directive
• 7217: The val in 'ALIGN=val' must be an integer ranging from 0 through 16.
• 7218: This is not an allowable attr keyword for a CDEC$ PSECT directive.
• 7219: This directive is not supported on this platform.
• 7220: Invalid syntax for CDEC$ directive; directive will be ignored.
• 7221: Keyword expected.
• 7222: There is no visible blank common block.
• 7223: There is no visible common block by this name.
• 7224: The keyword 'ALIGN' is expected.
• 7225: Multiple declaration of a pointee.
• 7226: An integer pointer variable has been explicitly given a data type that is not the integer type and kind for an address on the current platform.
• 7227: An integer pointer variable cannot also be a DEC Fortran pointee
• 7228: An integer pointer cannot have the Fxx ALLOCATABLE attribute
• 7229: An integer pointer cannot have the Fxx POINTER attribute
• 7230: An integer pointee cannot have the Fxx ALLOCATABLE attribute
• 7231: An integer pointee cannot have the Fxx POINTER attribute
• 7232: An integer pointee cannot have the DEC AUTOMATIC attribute
• 7233: An integer pointee cannot have the DEC STATIC attribute
• 7234: An integer pointee cannot have the Fxx SAVE attribute
• 7235: An OpenMP* SECTIONS directive is not permitted in the dynamic extent of a CRITICAL, MASTER, or ORDERED directive.
• 7236: An OpenMP* DO directive is not permitted in the dynamic extent of a CRITICAL, MASTER or ORDERED directive.
• 7237: An integer pointer variable cannot appear in an ASSIGN statement.
• 7238: An integer pointee cannot appear in a DATA statement.
• 7239: An integer pointer variable can appear in a DATA statement with literal values only.
• 7240: An integer pointee cannot appear in an EQUIVALENCE statement.
• 7241: An integer pointee cannot appear in a NAMELIST statement.
• 7242: An integer pointee cannot appear in an HPF directive.
• 7243: An integer pointer cannot appear in an HPF directive.
• 7244: There is an unmapped actual argument and the associated dummy argument has descriptive directives.
• 7245: If a dummy argument/result is aligned descriptively with another dummy argument/result, the align-target must have a descriptive alignment, or must have the inherit attribute, or must be descriptively distributed.
• 7246: REAL(KIND=16) is not yet supported with the -wsf switch.
• 7247: Mapped integer pointers are not yet supported with the -hpf/-numa switch.
• 7248: Variable format expressions are not yet supported with the -wsf switch.
• 7249: Initialization of VAX structures is not yet supported with the -wsf switch.
• 7250: This external, internal, or module function reference is not yet supported in I/O statements with the -wsf switch.
• 7251: Until long double is available in the host compiler, REAL(KIND=16) constants and arithmetic will be done as REAL(KIND=8).
• 7252: Each present argument of the SYSTEM_CLOCK intrinsic must be of an integer type and all present arguments must have the same kind type parameter.
• 7253: An argument of the SYSTEM_CLOCK intrinsic that is not of type default integer is not standard Fxx.
• 7254: This function is referenced in a forall-body-stmt and is not a PURE function.
• 7255: A forall-stmt-body must not be empty.
• 7256: Invalid array, function, substring, or structure-constructor reference.
• 7257: The characteristics of the procedure's arguments differ from those of the same procedure's arguments that are redefined in the INTERFACE statement.
• 7258: The characteristics of the subroutine/function differ from those of the same subroutine/function that is specified in the INTERFACE statement.
• 7259: The number of arguments of the subroutine/function differ from those of the same subroutine/function that is specified in the INTERFACE statement.
• 7260: A subobject designator for a parent that is a constant appears in a leftside context.
• 7261: For standard Fortran xx, a variable in a statement function expression must be a dummy argument of the statement function or a variable that is accessible in the same scoping unit as the statement function (R1226.5).
• 7262: Allowing a variable name that is not an array-variable-name as an actual argument for a corresponding array dummy is not standard Fortran xx.
• 7263: Allowing a comma in the length selector of a component-definition statement is not standard Fortran xx.
• 7264: A deferred shape array is not permitted in an OpenMP* FIRSTPRIVATE, LASTPRIVATE or REDUCTION clause.
• 7265: The DEC$ ATTRIBUTES ... directive is not supported in Fortran xx standard.
• 7266: A Fxx pointer is not permitted in an OpenMP* REDUCTION clause.
• 7267: Invalid argument for the LOC intrinsic function.
• 7268: The argument to the FREE procedure must be a DEC Fortran pointer variable.
• 7269: A CHARACTER*(*) variable is required for the second argument of the GETARG procedure.
• 7270: A character constant is required for string in ALIAS:string.
• 7271: Not a valid attribute for the DEC$ ATTRIBUTES directive.
• 7272: This attribute is not supported in the DEC$ ATTRIBUTES directive.
• 7273: This attribute appears more than once in a single DEC$ ATTRIBUTES directive.
• 7274: DEC$ ATTRIBUTES DLLIMPORT attribute can appear only in an interface-body.
• 7275: DEC$ ATTRIBUTES DLLEXPORT attribute can not be assigned to an internal procedure.
• 7276: This symbol has multiply declared DEC$ ATTRIBUTES DLLEXPORT attribute.
• 7277: This symbol has multiply declared DEC$ ATTRIBUTES C attribute.
• 7278: This symbol has multiply declared DEC$ ATTRIBUTES STDCALL attribute.
• 7279: Common block names are not permitted for the VALUE or REFERENCE attribute.
• 7280: This symbol has multiply declared VALUE attributes.
• 7281: This symbol has multiply declared DEC$ ATTRIBUTES REFERENCE{32|64] attribute.
• 7282: This symbol has multiply declared DEC$ ATTRIBUTES DLLIMPORT attribute.
• 7283: A dummy argument can not have both the DEC$ ATTRIBUTES REFERENCE and VALUE attribute.
• 7284: A global entity can not have both the DEC$ ATTRIBUTES DLLIMPORT and DLLEXPORT attribute.
• 7285: A global entity can not have both the DEC$ ATTRIBUTES C and STDCALL attribute.
• 7286: This symbol has multiply declared DEC$ ATTRIBUTES ALIAS attribute.
• 7287: A dummy argument has both the VALUE attribute and an explicit INTENT(OUT) Fxx attribute.
• 7288: Keyword PAGE, BYTE, WORD, LONG, QUAD, or OCTA expected.
• 7289: The PAGE keyword is not supported for this platform.
• 7290: The val in 'ALIGN=val' must be an integer ranging from 0 through 13.
• 7291: Keyword 'WARNINGS' or 'NOWARNINGS' expected.
• 7292: A dummy argument with the VALUE attribute cannot be an array or an array pointer.
• 7293: A function subprogram or subroutine subprogram cannot have the VALUE attribute.
• 7294: The use of this passed length character name in this context is not standard Fortran xx.
• 7295: An intrinsic procedure is not permitted in this context.
• 7296: The function result-name appears in a specification expression.
• 7297: Assigning numeric data to variables of CHARACTER type is not standard Fortran xx.
• 7298: Too large hex constant in this context.
• 7299: This namelist group object in this context cannot have private components.
• 7300: This derived-type object in an input-output list cannot have private components.
• 7301: The DEC$ PACK directive argument, if present, must have value 1, 2, 4, 8, 16 or 32.
• 7302: An inherited IMPLICIT mapping for a letter in this range has been used by a PARAMETER statement in this scoping unit; this new mapping conflicts.
• 7303: DEC$ ATTRIBUTES VARYING cannot be specified unless DEC$ ATTRIBUTES C is specified.
• 7304: Cannot specify DEC$ ATTRIBUTES EXTERN for use associated variables.
• 7305: DEC$ ATTRIBUTE EXTERN has been specified multiple times for this name.
• 7306: Common block names are not allowed for the DEC$ ATTRIBUTES EXTERN specifier.
• 7307: Common block names are not allowed for the DEC$ ATTRIBUTES VARYING specifier.
• 7308: DEC$ ATTRIBUTE VARYING has been specified multiple times for this name.
• 7309: The DEC$ ATTRIBUTES VARYING specifier is not supported for the current compiler option.
• 7310: The DEC$ ATTRIBUTES VARYING specifier can be used in an interface block for an explicit interface for a C/C++ routine or for a variable declared EXTERNAL that represents a C/C++ routine.
• 7311: The pointer assignment statement causes a DO variable to become (re)defined.
• 7312: The object-list is missing.
• 7313: For a given scoping unit, an AUTOMATIC statement for a specific symbol or the AUTOMATIC attribute is not permitted because the global AUTOMATIC condition is enabled.
• 7314: The global AUTOMATIC statement has occurred multiple times.
• 7315: This global AUTOMATIC statement conflicts with other AUTOMATIC statements and/or AUTOMATIC attributes for this scoping unit.
• 7316: Null components (probably caused by extra commas) in a structure constructor are invalid
• 7317: Standard Fxx requires that the absolute value of SHIFT, the 2nd argument, be less than or equal to SIZE, the 3rd argument.
• 7318: Standard Fxx requires the value of SIZE, the 3rd argument, be less than or equal to BIT_SIZE of I, the 1st argument.
• 7319: This argument's data type is incompatible with this intrinsic procedure; procedure assumed EXTERNAL.
• 7320: Standard Fxx requires that the type AND type parameters of the actual argument be the same as the type AND type parameters of the dummy argument.
• 7321: The leftmost part-ref in a data-ref can not be a structure constructor.
• 7322: Symbol not previously declared.
• 7323: Unused dummy argument.
• 7324: Only one SCHEDULE clause can be specified on this OpenMP* directive.
• 7325: The product of the extents of the explicit-shape-spec-list of the PROCESSORS directive must equal the n specified in -wsf n.
• 7326: Fortran xx does not allow this keyword on the OPEN statement.
• 7327: This statement is not permitted in an INTERFACE TO statement list
• 7328: Fortran xx does not allow this length specification in this position.
• 7329: The procedure name on the INTERFACE TO statement conflicts with a name in the encompassing scoping unit.
• 7330: This procedure is not supported as an HPF local library routine but is treated as an external procedure.
• 7331: The extents of an explicit-shape-spec for a pointee in a main program unit must be compile time constants.
• 7332: The extents of an explicit-shape-spec for a pointee in a BLOCK DATA unit must be compile time constants.
• 7333: The extents of an explicit-shape-spec for a pointee in the specification part of a module must be compile time constants.
• 7334: Fxx component is being referenced as if it were a structure type; this is not standard Fortran xx.
• 7335: There is a mixture of '%' and '.' separators in a single data-ref; this is NOT standard Fortran xx.
• 7336: There is a mixture of '%' and '.' separators in a single data-ref.
• 7337: Non-global variable with DEC$ ATTRIBUTES ALIAS makes no sense.
• 7338: Non-global variable with DEC$ ATTRIBUTES C makes no sense.
• 7339: The alignment or distribution specification for object in hpf_serial procedure is invalid.
• 7340: Non-global variable with DEC$ ATTRIBUTES DEFAULT makes no sense.
• 7341: Non-global variable with DEC$ ATTRIBUTES STDCALL makes no sense.
• 7342: The computed GOTO statement is an obsolescent feature in Fortran xx.
• 7343: A statement function is an obsolescent feature in Fortran xx.
• 7344: A DATA statement in the execution-part of a scoping unit is an obsolescent feature in Fortran xx.
• 7345: An assumed length CHARACTER function is an obsolescent feature in Fortran xx.
• 7346: The CHARACTER* form of a CHARACTER declaration is an obsolescent feature in Fortran xx.
• 7347: This intrinsic function in an initialization expression is not standard Fortran xx
• 7348: DO termination on a statement other than an END DO or CONTINUE has been deleted in Fortran 95.
• 7349: The use of real or double precision DO control variable has been deleted in Fortran xx.
• 7350: The assign GO TO statement has been deleted in Fortran xx.
• 7351: This intrinsic function in a specification expression is not standard Fortran xx
• 7352: Use of real or double precision DO loop control expression has been deleted in Fortran xx.
• 7353: Only one DEFAULT clause can be specified on this OpenMP* directive.
• 7354: Branching to an END IF stmt from outside its IF block has been deleted in Fortran xx. Branch to the statement following the END IF.
• 7355: The alternate return is an obsolescent feature in Fortran xx.
• 7356: The PAUSE statement has been deleted in Fortran xx.
• 7357: The ASSIGN statement has been deleted in Fortran xx.
• 7358: Assigned FORMAT specifiers have been deleted in Fortran xx.
• 7359: The cH edit descriptor has been deleted in Fortran xx.
• 7360: A masked ELSEWHERE statement occurred without a corresponding WHERE statement.
• 7361: Only array assignment-stmt, where-stmt, where-construct-stmt, elsewhere-stmt, masked-elsewhere-stmt, or endwhere-stmt permitted.
• 7362: The mask-expr on the masked-elsewhere-stmt does not conform with the mask-expr for the where-construct.
• 7363: Standard Fxx does not allow a dummy argument to a pure function to be used in a variable definition context.
• 7364: The argument to the ALLOCATED intrinsic cannot be a coindexed object.
• 7365: A forall-construct-name is not supported in Fortran xx standard.
• 7366: DEC$ ATTRIBUTES DLLIMPORT is ignored for non-external procedure.
• 7367: The data value NULL() can only be assigned to a Fortran POINTER.
• 7368: A Fortran POINTER can only be data loaded to NULL().
• 7369: MOLD must be a pointer.
• 7370: A parameter cannot have the POINTER attribute nor can '=>' appear in the initialization.
• 7371: An object in a COMMON block with DEC$ ATTRIBUTES DLLIMPORT cannot be initialized.
• 7372: Procedures as pointees is not supported in Fortran xx standard.
• 7373: Fixed form source is an obsolescent feature in Fortran xx.
• 7374: Fxx standard requires all arguments be of the same type and same kind type parameter.
• 7375: Standard Fxx requires POS, the 2nd argument, be non-negative.
• 7376: Standard Fxx requires POS, the 2nd argument, be less than BIT_SIZE of I, the 1st argument.
• 7377: Standard Fxx requires POS, the 2nd argument, + LEN, the 3rd argument, be less than or equal to the BIT_SIZE of I, the 1st argument.
• 7378: Standard Fxx requires the absolute value of SHIFT, the 2nd argument, be less than or equal to the BIT_SIZE of I, the 1st argument.
• 7379: Standard Fxx requires LEN, the 3rd argument, be non-negative.
• 7380: Standard Fxx requires SIZE, the 3rd argument, be non-negative.
• 7381: The distributee is not a component defined in the derived-type-def
• 7382: The alignee is not a component defined in the derived-type-def.
• 7383: A component of a derived type may be explicitly mapped only if the type of the component is not an explicitly mapped type.
• 7384: A variable or array of a derived type may be explicitly mapped only if the derived type is not an explicitly mapped type.
• 7385: An alignee in an ALIGN directive may not be a structure-component.
• 7386: An distributee in a DISTRIBUTE directive may not be a structure-component.
• 7387: Only one IF clause can be specified on this OpenMP* directive.
• 7388: Only one NUMA/ORDERED clause can be specified on this OpenMP* directive.
• 7389: The DEC$ PASCAL attribute is ignored.
• 7390: The data-object has the POINTER attribute and '=>' does not appear in the initialization.
• 7391: S, the second argument, cannot be zero.
• 7392: NCOPIES, the second argument, cannot be negative.
• 7393: Since the physical representation of the result is longer than that of SOURCE, the physical representation of the leading part is that of SOURCE and the remainder is undefined.
• 7394: Converting this constant to the kind type of its expression level sibling (which is of lower kind) is not standard Fxx.
• 7395: A CHARACTER constant or a CHARACTER expression is not permitted here
• 7396: Passing this intrinsic procedure as an actual argument is not standard Fortran xx.
• 7397: An array dummy argument of an 'EXTRINSIC(HPF_LOCAL)' procedure called from a non-HPF_LOCAL procedure must be an assumed shape array.
• 7398: An extrinsic-prefix is not [yet] supported in a program-stmt.
• 7399: An extrinsic-prefix is not [yet] supported in a module-stmt.
• 7400: An extrinsic-prefix is not [yet] supported in a block-data-stmt.
• 7401: The generic-spec may be included in the end-interface-stmt only if it was provided in the interface-stmt.
• 7402: The generic-spec included in the end-interface-stmt does not agree with the generic-spec on the interface-stmt
• 7403: End of statement expected.
• 7404: A subroutine with the ELEMENTAL prefix-spec shall not contain an asterisk (*) in its dummy-argument-list
• 7405: The ELEMENTAL prefix-spec was not part of Fortran 90.
• 7406: Fortran xx standard does not permit an entry point variable to be referenced before the entry declaration itself.
• 7407: Unresolved MODULE PROCEDURE specification name.
• 7408: A variable in the NEW or REDUCTION clause of the INDEPENDENT directive may not be an object in COMMON or storage associated with an object in COMMON.
• 7409: A delimiter is missing or invalid. Any of the following delimiters are valid: , $ / : ) or end-of-format list.
• 7410: Fortran xx does not allow this keyword.
• 7411: An is invalid in this context.
• 7412: In a format list, the character following the P edit descriptor is invalid.
• 7413: The scale factor in the format list is either missing or invalid.
• 7414: The format list contains an extra right parenthesis as a delimiter.
• 7415: The format list is missing parentheses as delimiters.
• 7416: Fortran xx does not allow this intrinsic procedure.
• 7417: Fortran xx requires w (field width) information in this context.
• 7418: A signed constant is invalid in this context.
• 7419: Either an E specifier for an exponent or a delimiter is missing.
• 7420: A dot (.) must appear in a format list in this context.
• 7421: A constant or general expression must appear in a format list in this context.
• 7422: Fortran xx requires w.d (field width.number of characters to right of decimal) information in this context.
• 7423: Fortran xx requires a count prefix for the X edit descriptor.
• 7424: A digit must appear in a format list in this context.
• 7425: A dot (.) is invalid in a format list in this context.
• 7426: A variable in the NEW or REDUCTION clause of the INDEPENDENT directive may not be use associated.
• 7427: Fortran xx does not allow the XOR operator for expressions.
• 7428: A variable in the NEW or REDUCTION clause of the INDEPENDENT directive may not be host associated.
• 7429: This format list edit descriptor must not be repeated.
• 7430: A function with the ELEMENTAL prefix-spec shall be defined as scalar.
• 7431: A function with the ELEMENTAL prefix-spec shall not have the POINTER attribute.
• 7432: A dum-arg of a procedure with the ELEMENTAL prefix-spec shall be defined as scalar.
• 7433: A dum-arg of a procedure with the ELEMENTAL prefix-spec shall not have the POINTER attribute.
• 7434: A dum-arg of a procedure with the ELEMENTAL prefix-spec shall not be a dummy procedure.
• 7435: An act-arg of an elemental procedure does not conform with its predecessor act-args.
• 7436: In a reference to an elemental subroutine, either all act-args shall be scalar, or all act-args associated with INTENT(OUT) and INTENT(INOUT) dum-args shall be conforming arrays.
• 7437: The type/rank/keyword signature for this elemental specific procedure conflicts with another specific procedure that shares the same generic-name.
• 7438: The type/rank/keyword signature for this specific procedure conflicts with an elemental specific procedure that shares the same generic-name.
• 7439: An INDEPENDENT directive can not be applied to a DO 'forever' do-stmt.
• 7440: Parallel_directives (PPD) are not available in Fortran xx standard.
• 7441: This parallel_directive is not [yet] supported.
• 7442: GEM-specific-directives are not available in Fortran xx standard.
• 7443: This DEC loop optimization directive is not [yet] supported.
• 7444: A PPD taskcommon-directive references a non-existent common block.
• 7445: A PPD taskcommon-directive for a named common block must appear before the Fxx common block declaration.
• 7446: Multiple or conflicting PPD taskcommon-directive for one named common block.
• 7447: Misplaced part of a PPD parallel-directive.
• 7448: The PPD directives stack limit has been exceeded.
• 7449: A PPD END directive occurred when there are no PPD block parallel-directives pending.
• 7450: This PPD END directive does not match the PPD block parallel-directive at the top of the stack.
• 7451: A PPD pdone-directive must appear lexically nested within a parallel-region.
• 7452: A PPD pdo-directive must appear lexically nested within a parallel-region.
• 7453: A PPD parallel-section-directive must appear lexically nested within a parallel-region.
• 7454: A PPD critical-section-directive must appear lexically nested within a parallel-region.
• 7455: A PPD copy-in-directive must appear lexically nested within a parallel-region.
• 7456: A PPD barrier-directive must appear lexically nested within a parallel-region.
• 7457: A PPD parallel-region-directive is lexically enclosed by another parallel-region-directive.
• 7458: A PPD parallel-do-directive must not appear lexically nested within a parallel region.
• 7459: Invalid copy-item in a PPD copy-in-directive.
• 7460: A common block name is required.
• 7461: A substring subobject is not [yet] supported as a copy-item on a PPD copy-in-directive.
• 7462: An array-section subobject is not [yet] supported as a copy-item on a PPD copy-in-directive.
• 7463: A structure-component subobject is not [yet] supported as a copy-item on a PPD copy-in-directive.
• 7464: A copy-item on a PPD copy-in-directive shall not be a SHARED variable.
• 7465: Unexpected identifier(...) encountered.
• 7466: Incorrect mode-keyword on PPD SCHEDTYPE directive/option.
• 7467: This statement or directive is not permitted within the body of a PPD critical-section-directive block.
• 7468: This statement or directive is not permitted within the body of a PPD parallel-region-directive block.
• 7469: This statement or directive is not permitted within the body of a PPD local-section of a PPD parallel-section-directive block.
• 7470: A PPD local-section must appear lexically within a PPD parallel-section-directive body.
• 7471: Not a valid PPD parallel-directive option for this context.
• 7472: A variable in blank common can not be specified as PPD LOCAL or SHARE.
• 7473: This PPD LOCAL or SHARE variable is part of a named common block that does not appear in a PPD taskcommon-directive.
• 7474: Assumed sized arrays may not be specified as PPD LOCAL
• 7475: Assumed shape arrays are not [yet] supported as PPD LOCAL or PPD SHARE.
• 7476: Blank common may not be specified as PPD LOCAL or SHARE.
• 7477: Named common block appearing in a PPD LOCAL or SHARE variable-or-common-list clause must also be referenced in a taskcommon-directive.
• 7478: Multiple PPD LOCAL option occurrences.
• 7479: Multiple PPD SHARE option occurrences.
• 7480: Multiple PPD LASTLOCAL option occurrences.
• 7481: Multiple PPD REDUCTION option occurrences.
• 7482: Object may not appear as both PPD SHARED and PPD LOCAL.
• 7483: This statement or directive is not permitted within the body of a PPD single-process-directive
• 7484: PPD local-section directive is required here.
• 7485: A PPD parallel-directive block starts in one F95 block and ends in another.
• 7486: This statement or directive is not permitted between the PPD pdo-directive/parallel-do-directive and the associated do-statement.
• 7487: There are unterminated PPD parallel directive and/or DEC loop optimization directive block[s].
• 7488: No valid do-statement to go with the pending PPD pdo-directive/parallel-do-directive.
• 7489: Implementation of PPD keymode RUNTIME is deferred.
• 7490: This is an invalid or unsupported PPD option.
• 7491: The integer kind type is too small for the 'latch' variable.
• 7492: Unexpected /.../ encountered.
• 7493: The statement following this DEC loop optimization directive must be an iterative do-stmt, a PPD pdo-directive, or a PPD parallel-do-directive.
• 7494: This DEC directive is not permitted in current scoping block.
• 7495: An ON or RESIDENT directive block starts in one F95 block and ends in another.
• 7496: An HPF END directive occurred when there were no ONN or RESIDENT directives pending.
• 7497: This HPF END directive does not match the HPF directive at the top of the stack.
• 7498: There are unterminated HPF ON or RESIDENT-directive block[s].
• 7499: HPF END without HPF BEGIN for ON or RESIDENT-directive.

Back to All Intel Fortran Compiler Diagnostics

• 8000: There is a conflict between local interface block and external interface block.
• 8001: The type of the element in a structure-constructor differs from the type of the component in the derived-type-def.
• 8002: An array name is required as the first option in a MEMORYTOUCH directive.
• 8003: Invalid data type for array used in MEMORYTOUCH directive.
• 8004: Invalid schedule or initialization type specified in a MEMORYTOUCH directive. Valid types are STATIC, DYNAMIC, GUIDED, RUNTIME, STORE, and LOAD.
• 8005: Invalid schedule type specified in SCHEDULE clause of a MEMORYTOUCH directive. Valid schedule types are STATIC, DYNAMIC, GUIDED, and RUNTIME
• 8006: Invalid initialization type specified in INITIALIZATION clause of a MEMORYTOUCH directive. Valid initialization types are STORE and LOAD
• 8007: Intrinsic operator can not be used as the name of a locally defined operator in an OPERATOR rename clause
• 8008: A common block or variable may not exceed 2147483647 bytes
• 8009: A pointer dummy argument with the INTENT(IN) attribute shall not appear as an allocate-object in an allocate or a deallocate statement.
• 8010: A pointer dummy argument with the INTENT(IN) attribute shall not appear as an pointer-object in a pointer-assignment-stmt or nullify-stmt.
• 8011: A pointer dummy argument with the INTENT(IN) attribute shall not appear as an actual argument if the associated dummy argument has the INTENT(OUT) or INTENT(INOUT) attribute.
• 8012: Fortran xx does not allow this sequence of length selector and array specifier.
• 8013: The dummy argument of a derived type containing a pointer component has the INTENT(IN) attribute therefore it shall not appear as the expr of an assignment-stmt in a PURE procedure.
• 8014: The common-block-object, or object storage associated with a common-block-object of a derived type containing a pointer component shall not appear as the expr of an assignment-stmt in a PURE procedure.
• 8015: The use associated object of a derived type containing a pointer component shall not appear as the expr of an assignment-stmt in a PURE procedure.
• 8016: The host associated object of a derived type containing a pointer component shall not appear as the expr of an assignment-stmt in a PURE procedure.
• 8017: The memory reference associated with an ASSUME_ALIGNED directive must be an array or subscripted array reference.
• 8018: The memory reference associated with an ASSUME_ALIGNED directive must not be in COMMON, a field reference, use associated, or host associated.
• 8019: Invalid alignment value specified for ASSUME_ALIGNED directive.
• 8020: The first argument to MM_PREFETCH must be an address.
• 8021: Intrinsic operator can not be used on the right hand side of an OPERATOR rename clause
• 8022: A locally defined operator name has been used multiple times.
• 8023: The shift count must be positive.
• 8024: The shift count must be non-negative and less than or equal to 64.
• 8025: An error occurred converting to an INTEGER(2) value.
• 8026: An error occurred converting to an INTEGER(4) value.
• 8027: An error occurred converting to an INTEGER(8) value.
• 8028: An error occurred converting to a REAL(4) value.
• 8029: An error occurred converting to a REAL(8) value.
• 8030: An error occurred converting to a REAL(16) value.
• 8031: Use of EXTERNAL to match subroutine argument in generic resolution is non-standard
• 8032: Generic procedure reference has two or more specific procedure with the same type/rank/keyword signature.
• 8033: This equivalence-object has the PROTECTED attribute, all of the objects in the equivalence set shall have the PROTECTED attribute.
• 8034: Vector subscripts followed by other vector subscripts or slices in data initialization is currently not implemented
• 8035: The double precision arguments to the DPROD intrinsic function are not standard conforming.
• 8036: A Hollerith constant is not allowed in this context
• 8037: If an object of a type for which component-initialization is specified appears in the specification-part of a MODULE and does not have ALLOCATABLE or POINTER attribute, the object shall have the SAVE attribute.
• 8038: A referenced intrinsic procedure can not have the same name as a common block.
• 8039: The INTENT(OUT) or INTENT(INOUT) attribute is not allowed for arguments received by value.
• 8040: Invalid type-name in a derived type definition.
• 8041: The IMPORT statement is not positioned correctly within the scoping unit.
• 8042: This argument must be of type character of length 1.
• 8043: The extra characters in the format specification will be ignored
• 8044: Declaring a FUNCTION subprogram without an argument list is non-standard
• 8045: Renaming user defined operators in USE statement is an extension of Standard Fxx.
• 8046: The 'KIND' argument for this intrinsic function is an extension of Standard Fxx.
• 8047: The IOMSG= specifier is an extension of Standard Fxx.
• 8048: An equivalenced data object must not be a structure component (field) of a derived type.
• 8049: Fortran xx does not allow branching to an END SELECT stmt from outside its CASE construct. Branch to the statement following the END SELECT.
• 8050: The IMPORT statement is not supported on this platform.
• 8051: The data type of the argument to HUGE is invalid.
• 8052: The data type of the argument to TINY is invalid.
• 8053: The data type of the argument to EPSILON is invalid.
• 8054: It is invalid to specify a common block on an IMPORT statement.
• 8055: The procedure has a dummy argument that has the ALLOCATABLE, ASYNCHRONOUS, OPTIONAL, POINTER, TARGET, VALUE or VOLATILE attribute. Required explicit interface is missing from original source.
• 8056: The ASYNCHRONOUS= specifier value in a data transfer statement is not known at compile time; the specifier will be ignored.
• 8057: Asynchronous input/output is not implemented in internal routines therefore this statement will be executed synchronously.
• 8058: Asynchronous input/output does not support variable format expression; therefore this statement will be executed synchronously.
• 8059: The module-name on a USE statement can not be used with both an INTRINSIC and NON_INTRINSIC module-nature specified.
• 8060: A dummy argument with the VALUE attribute can not have the VOLATILE attribute (Constraint C527).
• 8061: A dummy argument with the VALUE attribute can not have the EXTERNAL attribute (Constraint C527).
• 8062: A dummy argument with the VALUE attribute can not have the POINTER attribute (Constraint C527).
• 8063: The character length of a dummy argument with the VALUE attribute must be an initialization expression (Constraint C528).
• 8064: This syntax is invalid; the keyword C is required when using the BIND attribute.
• 8065: This syntax is invalid; the keyword NAME is required in NAME= specifier when using the BIND attribute.
• 8066: The NAME= specifier in BIND statement or in the BIND attribute specification of a type declaration statement must be a character initialization expression.
• 8067: If any bind-entity in a bind-stmt is an entity-name, the bind-stmt shall appear in the specification part of a module (Constraint C550).
• 8068: If the language-binding-spec has a NAME= specifier, the bind-entity-list shall consist of a single bind-entity (Constraint C551).
• 8069: This symbol has multiple BIND statement/attribute declarations which is not allowed.
• 8070: The ASYNCHRONOUS= specifier in a data transfer statement must be a character initialization expression (Constraint C924).
• 8071: An integer constant expression is required in this context; the directive will be ignored.
• 8072: This keyword is invalid for the LOOPCOUNT directive; the directive will be ignored.
• 8073: The LOOPCOUNT directive only allows 1 MIN, MAX and AVG keyword specified; the directive will be ignored.
• 8074: The LOOPCOUNT directive with keywords is not supported in this release; the directive will be ignored.
• 8075: The argument SHIFT to the SHIFTA/SHIFTR/SHIFTL intrinsic function is out-of-range.
• 8076: A proc-language-binding-spec is not standard Fortran xx.
• 8077: A proc-language-binding-spec shall not be specified for an internal procedure.
• 8078: A derived type with the BIND attribute is not standard Fortran xx.
• 8079: A derived type with the BIND attribute shall not be SEQUENCE type
• 8080: Each component of a derived type with the BIND attribute shall be a nonpointer, nonallocatable data component with interoperable type and type parameters
• 8081: The variable with the BIND(C) attribute shall not appear in common block.
• 8082: The NULLIFY attribute may only be used for a dummy argument that has both the POINTER and INTENT(OUT) attributes.
• 8083: The DLLEXPORT attribute should not be specified for a type.
• 8084: An internal file unit must be of type character.
• 8085: A procedure entry and the procedure must have the same use of the STDCALL attribute.
• 8086: This host associated name shall not appear as a construct name.
• 8087: The characteristics of the result of the function named in the FUNCTION statement are not standard conforming.
• 8088: The characteristics of the result of the function named in the ENTRY statement are not standard conforming.
• 8089: Parentheses around an I/O list is an extension to Standard Fxx.
• 8090: There are more than 5 decimal digits specified in a STOP or PAUSE statement. This is an extension to Standard Fxx.
• 8091: Invalid argument greater than 2147483647 in either a PAUSE, STOP or ERROR STOP statement.
• 8092: A do-variable within a DO body shall not appear as a stat-variable in an allocate or a deallocate statement.
• 8093: A do-variable within a DO body shall not appear in a variable definition context.
• 8094: The array-spec for a function name with ALLOCATABLE or POINTER attribute must be a deferred-shape-array.
• 8095: The name of the internal procedure conflicts with a procedure name in the MODULE PROCEDURE statement.
• 8096: The use-name in the rename clause has not been resolved in the module.
• 8097: This name has the EXTERNAL attribute, therefore it shall not be declared with VOLATILE attribute.
• 8098: DEC$ OPTIMIZE directive must be within the body of a procedure program unit; directive ignored.
• 8099: The rank of the function reference does not match the rank of the function definition.
• 8100: The actual argument is an array section or assumed-shape array, corresponding dummy argument that has either the VOLATILE or ASYNCHRONOUS attribute shall be an assumed-shape array.
• 8101: The actual argument is a pointer array, corresponding dummy argument that has either the VOLATILE or ASYNCHRONOUS attribute shall be an assumed-shape array or a pointer array.
• 8102: The name of this intrinsic module has been previously referenced as non-intrinsic in this scoping unit.
• 8103: The name of this non-intrinsic module has been previously referenced as intrinsic in this scoping unit.
• 8104: A common-block-object of a nonsequence derived type is an extension of Standard Fxx.
• 8105: Required explicit interface for an elemental procedure is missing from original source.
• 8106: This binary constant is too large in this context.
• 8107: Required explicit interface for a procedure with BIND attribute is missing from original source.
• 8108: The data-i-do-object shall be an array-element, scalar-structure-component or data-implied-do.
• 8109: The scalar-structure-component is used as a data-i-do-object. It shall contain at least one part-ref that contains a subscript-list.
• 8110: The module file for compiler-generated interface was generated for a different platform or by an incompatible compiler or compiler release. It cannot be read. Use -gen-interfaces option.
• 8111: The same name cannot be specified more than once in an ALLOCATE statement.
• 8112: The same name cannot be specified more than once in a DEALLOCATE statement.
• 8113: Fxx standard only allows CHARACTER(LEN=1) arrays with BIND(C).
• 8114: This intrinsic procedure reference must not have more than one argument present.
• 8115: The argument BOUNDARY to the EOSHIFT intrinsic function shall not be omitted when the argument ARRAY is of a derived type.
• 8116: DLLIMPORT and DLLEXPORT symbols may not be specified as COPYPRIVATE, FIRSTPRIVATE, LASTPRIVATE, PRIVATE, or THREADPRIVATE.
• 8117: DLLIMPORT and DLLEXPORT symbols may not be specified in a COPYIN or REDUCTION list.
• 8118: DLLIMPORT and DLLEXPORT symbols may not default to PRIVATE or FIRSTPRIVATE in a parallel region.
• 8119: The character length of a dummy argument with the VALUE attribute must be 1. Only the first character is passed.
• 8120: The character length of a dummy argument with the VALUE attribute may not be zero.
• 8121: A data-stmt-object shall not be a subobject of a pointer.
• 8122: An unterminated block exists before a CASE statement
• 8123: %VAL or %REF is invalid in this context.
• 8124: In a format list, the required scale factor for the P edit descriptor is missing. This is an extension to Standard Fxx.
• 8125: This type conflicts with a previous implicit typing of a namelist group object with the same name, it is prohibited by Fortran standard
• 8126: An equivalence-object shall not be a variable with the BIND attribute or a variable in a common block that has the BIND attribute.
• 8127: A null argument is not permitted when calling a Fortran routine which has an explicit interface defined.
• 8128: The BIND attribute of the associated actual procedure differs from the BIND attribute of the dummy procedure.
• 8129: A common-block-object which is neither a sequence derived type nor a derived type with the BIND attribute is an extension of Standard Fxx.
• 8130: Nested enumeration definitions are not permitted.
• 8131: An END ENEM statement occurred without a corresponding ENUM statement.
• 8132: This syntax is invalid; the BIND(C) attribute is required on an enumeration statement.
• 8133: This statement is not permitted within an enumeration.
• 8134: An enumeration must have at least one ENUMERATOR statement.
• 8135: The value of the enumerator must be a scalar integer initialization expression.
• 8136: This ENUMERATOR constant name is invalid in this context.
• 8137: The ENUMERATOR constant name cannot have the target/pointer/adjustable attribute.
• 8138: The syntax is incorrect, the keyword BIND is expected in this context.
• 8139: An END ENUM statement is missing in an enumeration definition.
• 8140: The argument for UNROLL or UNROLL_AND_JAM must be an integer constant expression in the range 0 through 255.
• 8141: A variable is required in the list associated with the VECTOR NONTEMPORAL directive.
• 8142: The specification-part of a PURE procedure shall specify that all its dummy procedures are PURE.
• 8143: The BIND(C) attribute for this symbol conflicts with a DEC$ ATTRIBUTES ALIAS, DECORATE, STDCALL, C, [NO_]MIXED_STR_LEN_ARG or REFERENCE attribute for this symbol.
• 8144: ASSOCIATE construct is not available in Fortran xx
• 8145: The ASSOCIATE constructs are nested too deeply.
• 8146: An END ASSOCIATE occurred without a corresponding ASSOCIATE statement.
• 8147: DO construct with a construct name must be terminated by an ENDDO statement with the same name.
• 8148: STAT= may not appear more than once in an ALLOCATE or a DEALLOCATE statement.
• 8149: Source expression in SOURCE= or MOLD= specifiers may not appear more than once in an ALLOCATE statement.
• 8150: An object with the PROTECTED attribute may not be the ERRMSG= variable in an ALLOCATE or DEALLOCATE statement.
• 8151: Fortran xx does not allow ERRMSG= keyword in an ALLOCATE or a DEALLOCATE statement.
• 8152: Neither the ERRMSG= variable nor any part of the source expression in SOURCE= or MOLD= specifiers may be allocated in the ALLOCATE statement in which it appears.
• 8153: If SOURCE= appears, the ALLOCATE statement may contain only one object to allocate.
• 8154: In an ALLOCATE statement the SOURCE= expression must be a scalar or have the same rank as the object being allocated.
• 8155: In an ALLOCATE statement the source expression in SOURCE= or MOLD= specifiers must be of the same type and kind type parameters as the object being allocated.
• 8156: The ERRMSG= variable must not be deallocated in the DEALLOCATE statement in which it appears.
• 8157: If source expression in SOURCE= or MOLD= specifiers in an ALLOCATE statement, a TYPE specification must not appear for the object being allocated.
• 8158: Fortran xx does not allow SOURCE= specifier in an ALLOCATE statement.
• 8159: Only STAT=, ERRMSG=, SOURCE= and MOLD= are allowed as specifiers in ALLOCATE statement.
• 8160: ERRMSG= may not appear more than once in an ALLOCATE or a DEALLOCATE statement.
• 8161: The SCALAR argument of the ALLOCATED inquiry intrinsic function shall be an allocatable scalar.
• 8162: The fxx standard requires that the argument of the ALLOCATED inquiry intrinsic function shall be an allocatable array.
• 8163: Only STAT= and ERRMSG= are allowed as options in DEALLOCATE statement.
• 8164: A generic interface name shall not be used as an actual argument.
• 8165: Fortran xx standard does not allow a CHARACTER type of argument in this intrinsic procedure.
• 8166: Multiple OMP COLLAPSE clauses in a parallel region are not allowed
• 8167: COLLAPSE operand must be an integer expression
• 8168: Parentheses are required after the PROCEDURE keyword.
• 8169: The specified interface is not declared.
• 8170: The passed-object dummy argument is missing from the procedure interface.
• 8171: This is not a valid attribute for the procedure declaration statement.
• 8172: This is not a valid attribute for the procedure component definition statement.
• 8173: The PASS and NOPASS attributes must not be both specified.
• 8174: The POINTER attribute must be specified for a procedure component definition.
• 8175: The NOPASS attribute must be specified for a procedure component with an implicit interface.
• 8176: The default passed-object dummy argument is missing from the procedure interface (may need the NOPASS attribute).
• 8177: The POINTER attribute must be specified if the procedure has the INTENT or SAVE attribute.
• 8178: The procedure pointer and the procedure target must have matching arguments.
• 8179: The procedure pointer and the procedure target must both be functions or subroutines.
• 8180: The procedure pointer and the procedure target must have matching result types.
• 8181: An ALLOCATE object must not be a procedure pointer.
• 8182: The name is neither an abstract interface nor a procedure with an explicit interface.
• 8183: This intrinsic procedure is not allowed as an interface name in the procedure statement.
• 8184: This intrinsic procedure is not allowed as a procedure target.
• 8185: A procedure pointer must not be specified with the BIND attribute with a NAME= specifier.
• 8186: A dummy procedure must not be specified with the BIND attribute with a NAME= specifier.
• 8187: Only one procedure is allowed in a procedure declaration statement if the BIND attribute with a NAME= is specified.
• 8188: An interface name should be specified in a procedure declaration statement if the BIND attribute is specified.
• 8189: The interface name should also be declared with the BIND attribute.
• 8190: Argument checking is not yet supported for procedures declared with an intrinsic procedure as interface.
• 8191: The procedure target must be a procedure or a procedure pointer.
• 8192: A procedure declaration statement is not standard Fortran xx.
• 8193: A procedure component is not standard Fortran xx.
• 8194: The COLLAPSE clause requires perfectly nested loops: no code may appear before or after the loops being collapsed.
• 8195: The argument to the MOVE_ALLOC intrinsic subroutine shall be an allocatable object.
• 8196: An ALLOCATE shape must not be given for a scalar object.
• 8197: A shape specification or a SOURCE expression must be given for an array.
• 8198: If the ALLOCATE object is an array and there is no allocate shape specification, source expression in SOURCE= or MOLD= specifiers must appear with the same rank as the ALLOCATE object.
• 8199: The fxx standard requires a shape specification when the ALLOCATE object is an array.
• 8200: SOURCE= expression does not conform with an ALLOCATE shape.
• 8201: Associate name cannot be a pointer
• 8202: A type with the EXTENDS attribute cannot also include the BIND attribute or SEQUENCE property.
• 8203: The parent of an extended type must be a previously defined type.
• 8204: The parent of an extended type cannot have the BIND attribute or SEQUENCE property.
• 8205: A component declared in an extended type cannot have the same name as any accessible component of its parent type.
• 8206: A BIND or EXTENDS attribute may be specified only once per type declaration.
• 8207: A derived type with the EXTENDS attribute is not standard Fortran xx.
• 8208: If type specification is omitted, each ac-value expression in the array constructor of type CHARACTER must have the same length type parameters.
• 8209: If type specification is omitted, each element in an array-constructor must have the same type and kind type parameters.
• 8210: Fortran xx does not allow type specification in an array constructor.
• 8211: This component-spec has already been specified.
• 8212: Omitted field is not initialized. Field initialization missing:
• 8213: A keyword in the structure constructor is not the name of a type component.
• 8214: Fxx standard requires all arguments be of default integer type
• 8215: FROM and TO arguments of IMVBITS must be of type INTEGER(2)
• 8216: FROM and TO arguments of HMVBITS must be of type INTEGER(2)
• 8217: FROM and TO arguments of BMVBITS must be of type INTEGER(1)
• 8218: Associate name cannot appear in an ASSIGN statement.
• 8219: Fortran xx does not allow a subroutine dummy argument to be used in generic selection
• 8220: An integer constant outside the default integer range is not standard Fortran xx - using INTEGER(4).
• 8221: An integer constant outside the default integer range is not standard Fortran xx - using INTEGER(8).
• 8222: Missing comma, dash, or right paren.
• 8223: An entity declared with the CLASS keyword shall be a dummy argument or have the ALLOCATABLE or POINTER attribute.
• 8224: A derived type used with the CLASS keyword shall not have the BIND attribute or SEQUENCE property.
• 8225: The CLASS keyword is not standard Fortran xx.
• 8226: The variable typing occurred after the DATA statement and changed its implicit typing.
• 8227: The type of the target is not a dynamic type of the pointer.
• 8228: An array dimension specification preceded by a character length is not standard Fortran xx.
• 8229: Fortran xx does not allow type specification in an allocate statement.
• 8230: In an ALLOCATE statement the type parameter values in type specification must be the same as a corresponding nondeferred values of the objects being allocated.
• 8231: In an ALLOCATE statement the type parameter values in type specification shall be an asterisk if and only if each object being allocated is a dummy argument for which the type parameter is assumed.
• 8232: If any object being allocated in the ALLOCATE statement has deferred type parameter, either type specification or SOURCE= or MOLD= specifiers shall appear.
• 8233: If any object being allocated in the ALLOCATE statement is unlimited polymorphic, either type specification or SOURCE= or MOLD= specifiers shall appear.
• 8234: If type specification appears, it shall specify a type with which each object being allocated is type compatible.
• 8235: If type specification appears, the type and kind type parameters of each object being allocated must be the same as type and kind type parameters of the type specification.
• 8236: Deferred character length in a data object or component declaration is an extension of Standard Fxx.
• 8237: The character length in a component declaration shall either be a colon, be an initialization expression, or be a specification expression.
• 8238: A colon may be used as a type parameter value only in the declaration of an entity or component that has the POINTER or ALLOCATABLE attribute.
• 8239: Type of this field is PRIVATE, Standard Fxx does not allow such fields in public types.
• 8240: The kind type parameter of this argument is too small.
• 8241: A function or subroutine name within an ABSTRACT INTERFACE block can not be the same as the name of an intrinsic type
• 8242: SELECT TYPE construct is not available in Fortran xx
• 8243: A type guard exists without a preceding SELECT TYPE statement.
• 8244: An unterminated block exists before a TYPE IS/CLASS IS statement
• 8245: SELECT TYPE statement must be immediately followed by CLASS IS, TYPE IS, CLASS DEFAULT or END SELECT statement.
• 8246: Only one type guard expression of the SELECT TYPE statements may be DEFAULT.
• 8247: Selector in SELECT TYPE statements must be polymorphic value.
• 8248: Duplicate type guard in SELECT TYPE
• 8249: Type in TYPE IS or CLASS IS statement is unrelated to the type of selector in SELECT TYPE statement
• 8250: The argument to the SAME_TYPE_AS intrinsic function must be an object of extensible type.
• 8251: An input item must not appear as the implied-DO variable of any implied-DO loop that contains the input item.
• 8252: A DATA implied-DO variable must be an array element or scalar structure component that has at least one subscript list.
• 8253: If selector expression in SELECT TYPE is not a named variable, associate-name=> shall appear.
• 8254: A type bound procedure is an extension of Standard Fxx.
• 8255: The DEFERRED and NON_OVERRIDABLE attributes must not be both specified.
• 8256: If an interface name appears in the type bound procedure definition statement, a DEFERRED attribute must appear.
• 8257: This is not a valid attribute for the type bound procedure definition statement.
• 8258: The interface name in the type bound procedure definition statement must be the name of an abstract interface or of a procedure that has an explicit interface.
• 8259: The type bound procedure definition statement must contains only one binding name.
• 8260: If '=> procedure' name appears in the type bound procedure definition statement, an interface name must not appear.
• 8261: If DEFERRED attribute appears in the type bound procedure definition statement, an interface name must appear.
• 8262: The passed-object dummy argument must be dummy data object with the same declared type as the type being defined.
• 8263: The passed-object dummy argument must be a scalar, nonpointer, nonallocatable dummy data object.
• 8264: The passed-object dummy argument must be a polymorphic dummy data object if the type being defined is extensible.
• 8265: The CONTAINS statement in derived type definition is an extension of Standard Fxx.
• 8266: Standard Fxx does not allow an internal procedure to be a procedure target.
• 8267: A type with the ABSTRACT attribute cannot also include the BIND attribute or SEQUENCE property.
• 8268: A derived type with the ABSTRACT attribute is not standard Fortran xx.
• 8269: An ABSTRACT attribute may be specified only once per type declaration.
• 8270: A deferred binding may appear only in the definition of an abstract type.
• 8271: Standard Fxx does not allow an assumed length CHARACTER result for a PURE CHARACTER function.
• 8272: A SEQUENCE derived type cannot have any type-bound procedures.
• 8273: An inherited binding with the NON_OVERRIDABLE attribute must not be overridden.
• 8274: If either an overriding binding or an overridden binding has a passed-object dummy argument, then the other must also.
• 8275: An overriding binding must only have the DEFERRED attribute if the binding it overrides is deferred.
• 8276: If either an overriding binding or an overridden binding is PURE then the other must be also.
• 8277: If either an overriding binding or an overridden binding is ELEMENTAL then the other must be also.
• 8278: An overriding binding and its corresponding overridden binding must have the same number of dummy arguments.
• 8279: The passed-object dummy arguments of an overriding and overridden binding must correspond by name and position.
• 8280: An overriding binding and its corresponding overridden binding must both be either subroutines or functions with the same result type, kind, and shape.
• 8281: If the overridden binding is PUBLIC than the overriding binding cannot be PRIVATE.
• 8282: If any object being allocated in the ALLOCATE statement is of abstract type, either type specification or SOURCE= or MOLD= specifiers shall appear.
• 8283: If the dummy argument is an assumed-shape array, the value of the character length parameter of the actual argument must be agree with that of the dummy argument.
• 8284: If the actual argument is scalar, the dummy argument shall be scalar unless the actual argument is of type character or is an element of an array that is not assumed shape, pointer, or polymorphic.
• 8285: Fortran xx does not allow a NAMELIST group object to be an allocatable object, a pointer, or a variable of a type that has an ultimate component that is a pointer or an allocatable array.
• 8286: Fortran xx does not allow NAMELIST group object to be a function result.
• 8287: The parent type of this type bound procedure is use associated with the PRIVATE type bound procedure part
• 8288: A private type bound procedure is accessible only within the module containing the type definition
• 8289: A private component name is accessible only within the module containing the type definition
• 8290: Recommended relationship between field width 'W' and the number of fractional digits 'D' in this edit descriptor is 'W>=D+3'.
• 8291: Recommended relationship between field width 'W' and the number of fractional digits 'D' in this edit descriptor is 'W>=D+7'.
• 8292: Recommended relationship between field width 'W' and the number of fractional digits 'D' in this edit descriptor is 'W>=D+9'.
• 8293: Recommended relationship between field width 'W', the number of fractional digits 'D' and the number of exponential digits 'E' in this edit descriptor is 'W>=D+E+5'.
• 8294: This field width 'W' must be immediately followed by a dot (.)
• 8295: Source expression in SOURCE= or MOLD= specifiers or length type parameter must not depend on the value of the STAT= variable or the ERRMSG= variable
• 8296: A bound in the shape specification in an ALLOCATE must not depend on the value of the STAT= variable or the ERRMSG= variable
• 8297: The type specification in TYPE IS or CLASS IS statement must specify that each length type parameter is assumed
• 8298: The type specification in TYPE IS or CLASS IS statement must not specify a sequence derived type or a type with the BIND attribute
• 8299: Bad alignment for object. Please recompile the module.
• 8300: If a dummy argument is allocatable or a pointer, the associated actual argument shall be polymorphic if and only if the dummy argument is polymorphic.
• 8301: A component declared with the CLASS keyword shall have the ALLOCATABLE or POINTER attribute.
• 8302: A derived type definition without any component definition statement is an extension of Standard Fxx.
• 8303: The type bound procedure part in derived type definition must have at least one procedure binding statement.
• 8304: In an intrinsic assignment statement, variable shall not be polymorphic.
• 8305: The NAME= specifier in the language-binding-spec must be a character initialization expression with nonzero length.
• 8306: Associate name defined in ASSOCIATE or SELECT TYPE statements doesn't have ALLOCATABLE or POINTER attribute
• 8307: If a dummy argument is allocatable or a pointer, the associated actual argument shall have deferred length parameter if and only if the dummy argument has deferred length parameter.
• 8308: For the SPREAD intrinsic function, the rank of the SOURCE argument must be less than 7.
• 8309: A list item shall not be polymorphic unless it is processed by a user-defined derived-type input/output procedure.
• 8310: The sequence of extensions of this derived type is too long.
• 8311: If data reference is an array, the referenced type bound procedure must have the PASS and ELEMENTAL attributes
• 8312: The derived type specifier shall not specify an abstract type.
• 8313: The TYPE(derived-type-spec) shall not specify an abstract type.
• 8314: If the rightmost part-name is of abstract type, data-ref shall be polymorphic
• 8315: Declaration of the routine conflicts with a previous declaration.
• 8316: A NAMELIST group object must not be a CLASS object.
• 8317: A CONTAINS statement without any internal or module subprogram is an extension of Standard Fxx.
• 8318: A recursive allocatable component is an extension of Standard Fxx.
• 8319: A namelist-group-object must not be an assumed-size array.
• 8320: An array with nonconstant bounds is an extension of Standard Fxx.
• 8321: The rank of an array more then 15 is an extension of Standard Fxx.
• 8322: A deferred binding is inherited by non-abstract type; It must be overridden
• 8323: Duplicate option in CDEC$ directive.
• 8324: Conflicting options in CDEC$ directive.
• 8325: Subobjects are not allowed in PRIVATE/FIRSTPRIVATE/LASTPRIVATE clause; a named variable must be specified.
• 8326: Variables that appear in namelist statements may not appear in a PRIVATE/FIRSTPRIVATE/LASTPRIVATE clause.
• 8327: Duplicate variable in list.
• 8328: A variable in the PRIVATE clause must not be specified in the FIRSTPRIVATE/LASTPRIVATE clause.
• 8329: Fortran pointers, Cray pointers, and assumed-size arrays may not appear in a LASTPRIVATE clause.
• 8330: Polymorphic variables may not appear in a PRIVATE/FIRSTPRIVATE/LASTPRIVATE clause.
• 8331: Size may be specified only for array variables.
• 8332: Size of variable must be an integer expression.
• 8333: Privatized part of variable exceeds variable size.
• 8334: The argument I to the MASKR/MASKL intrinsic function must be non-negative.
• 8335: The argument I to the MASKR/MASKL intrinsic function is out-of-range.
• 8336: The arguments I and J must not both be boz-literal-constant.
• 8337: This boz-literal-constant is too large in this context and will be truncated on the left.
• 8338: A final subroutine name must be the name of a module procedure with exactly one dummy argument.
• 8339: The dummy argument of a final subroutine must be a variable of the derived type being defined and cannot be optional, pointer, allocatable, or polymorphic.
• 8340: The dummy argument of final subroutine must not have the INTENT (OUT) or VALUE attribute.
• 8341: Final subroutines are not inherited through type extension and cannot be overridden.
• 8342: A final subroutine name must not be the same as any other name previously specified as a final subroutine for the given type.
• 8343: A final subroutine shall not have a dummy argument with the same kind type parameters and rank as the dummy argument of another final subroutine of that type.
• 8344: A FINAL subroutine statement is an extension of Standard Fxx.
• 8345: A FINAL subroutine statement is permitted only within the type bound procedure part of a derived type.
• 8346: A function reference cannot be used as the leftmost part-ref of structure component.
• 8347: Coarray is not supported on this platform
• 8348: A coarray is not interoperable.
• 8349: A Cray pointer cannot be a coarray.
• 8350: A Cray pointee cannot be a coarray.
• 8351: An entity with the POINTER attribute shall not be a coarray.
• 8352: A coarray with the ALLOCATABLE attribute shall have a coarray-spec that is a deferred-coshape-spec list.
• 8353: An entity with the VALUE attribute shall be a dummy data object that is a coarray, and does not have a coarray ultimate component.
• 8354: The codimension specifications are incompatible.
• 8355: An entity with the AUTOMATIC attribute shall not be a coarray.
• 8356: A coarray component shall be a deferred-coshape-spec-list and have the ALLOCATABLE attribute.
• 8357: A coarray that does not have the ALLOCATABLE attribute shall have a coarray-spec that is an explicit coshape-spec.
• 8358: A coarray shall not be of type C PTR or C FUNPTR.
• 8359: An equivalence-object shall not be a coarray.
• 8360: A common-block-object shall not be a coarray.
• 8361: A coarray or an object with a coarray ultimate component shall be a dummy argument or have the ALLOCATABLE or SAVE attribute.
• 8362: Invalid coarray reference.
• 8363: An entity is not a coarray.
• 8364: There are missing arguments in an array reference.
• 8365: Image selector can't be subscript-triplet.
• 8366: The number of cosubscripts is incorrect.
• 8367: If CONTIGUOUS attribute is specified, the component must be an array with POINTER attribute
• 8368: An entity with CONTIGUOUS attribute must be an array
• 8369: An entity with the CONTIGUOUS attribute shall be an array pointer or an assumed-shape array.
• 8370: This symbol has multiple CONTIGUOUS statement/attribute declarations which is not allowed.
• 8371: If pointer is declared CONTIGUOUS, target must be contiguous as well.
• 8372: If dummy argument is declared CONTIGUOUS, actual argument must be contiguous as well.
• 8373: Array section is not contiguous if it has a vector subscript.
• 8374: Array section is not contiguous with such set of indices.
• 8375: Array section is not contiguous if it has stride other than unity.
• 8376: Substring of character array section is contiguous only if the substring range specifies all characters of the array item.
• 8377: An array is not contiguous if any part other than final has non-zero rank.
• 8378: Pointer array is not contiguous unless it is declared CONTIGUOUS.
• 8379: The argument SHIFT to the DSHIFTR/DSHIFTL intrinsic function is out-of-range.
• 8380: Attribute CONTIGUOUS is an extension of Standard Fxx.
• 8381: The type bound procedure cannot be passed as an actual argument.
• 8382: The dummy arguments of an overriding and overridden binding that correspond by position must have the same names.
• 8383: The dummy arguments of an overriding and overridden binding that correspond by position must have the same characteristics, except for the type of the passed object dummy arguments.
• 8384: COARRAY argument of IMAGE_INDEX intrinsic function shall be a coarray.
• 8385: SUB argument of IMAGE_INDEX intrinsic function shall be a rank-one integer array of size equal to the corank of COARRAY.
• 8386: COARRAY argument of THIS_IMAGE intrinsic function shall be a coarray.
• 8387: COARRAY argument of LCOBOUND/UCOBOUND intrinsic function shall be a coarray.
• 8388: Fortran xx does not allow MOLD= specifier in an ALLOCATE statement.
• 8389: Fortran xx does not allow G0 or G0.d format specifier.
• 8390: Fortran xx does not allow unlimited format item.
• 8391: An entity with the INTENT(OUT) attribute must not be an allocatable coarray or have a subobject that is an allocatable coarray.
• 8392: If the actual argument is a polymorphic coindexed object, the dummy argument must not be polymorphic.
• 8393: If the actual argument is a coindexed object with an allocatable ultimate component, the nonallocatable nonpointer dummy argument must have the INTENT (IN) or the VALUE attribute.
• 8394: If the actual argument is a coindexed object, the allocatable or pointer dummy argument must have the INTENT (IN) attribute.
• 8395: An actual argument that is a coindexed object with the ASYNCHRONOUS or VOLATILE attribute must not correspond to a dummy argument that has either the ASYNCHRONOUS or VOLATILE attribute.
• 8396: If the dummy argument is a coarray, the corresponding actual argument must be a coarray and must have the VOLATILE attribute if and only if the dummy argument has the VOLATILE attribute.
• 8397: The corank of the actual argument must be the same as that of the dummy argument.
• 8398: A dum-arg of a procedure with the ELEMENTAL prefix-pec must not be a coarray.
• 8399: Vector length must be an integer value that is a power of two and is between 2 and 16
• 8400: Duplicate value in list.
• 8401: Expression must be of basic type.
• 8402: Expression must be l-value.
• 8403: Named variable is expected.
• 8404: Step value must be of numeric type.
• 8405: Step value must be either a literal numerical constant or a variable.
• 8406: The REDUCTION clause operator must be +, *, -, MAX, MIN, .AND., .OR., .EQV., or .NEQV..
• 8407: The data type of the variable is not defined for the operator or intrinsic specified on the REDUCTION clause.
• 8408: The variable is specified in another REDUCTION clause.
• 8409: Directive SIMD must not be followed by another SIMD directive.
• 8410: Directive SIMD must be followed by counted DO loop.
• 8411: DO loop preceded by directive SIMD must not contain inner loops.
• 8412: DO loop preceded by directive SIMD must not contain EXIT statements.
• 8413: Either file number specifier or NEWUNIT specifier must be specified in OPEN statement.
• 8414: If NEWUNIT appears in OPEN statement either FILE or STATUS (with value SCRATCH) specifiers must appear.
• 8415: Either UNIT= specifier or NEWUNIT= specifier is required for OPEN statement.
• 8416: Unlimited format item shall be specified ONLY once.
• 8417: The sum of the rank and corank of a coarray shall not exceed 31.
• 8418: The sum of the rank and corank of a coarray more then 15 is an extension of Standard Fxx.
• 8419: Within the specification part of a module all GENERIC bindings with the same generic-spec must specify, either implicitly or explicitly, the same accessibility in the same derived type.
• 8420: If generic-spec is OPERATOR or ASSIGNMENT, each of its specific bindings must have a passed object dummy argument.
• 8421: A GENERIC type bound procedure name is not permitted to be the same as a specific type bound procedure name in the same type.
• 8422: If the component immediately preceding the type-bound procedure is abstract, the entire data reference before the procedure name must be polymorphic.
• 8423: In GENERIC type bound procedure definition each binding name must be the name of a specific binding of the type.
• 8424: A GENERIC binding is an extension of Standard Fxx.
• 8425: The argument N to the Bessel intrinsic function must be non-negative.
• 8426: The argument N1 to the Bessel intrinsic function must be non-negative.
• 8427: The argument N2 to the Bessel intrinsic function must be non-negative.
• 8428: The value of the argument X to the Bessel intrinsic function must be greater than zero.
• 8429: The value of the argument X must not be zero.
• 8430: Using constant expression as a stop code is an extension of Standard Fxx.
• 8431: A RETURN statement shall not appear within a DO CONCURRENT construct.
• 8432: An EXIT statement shall not belong to a DO CONCURRENT construct.
• 8433: A CYCLE statement shall not appear within the range of a DO CONCURRENT construct if it belongs to an outer construct.
• 8434: An EXIT statement shall not appear within the range of a DO CONCURRENT construct if it belongs to an outer construct.
• 8435: A reference to a nonpure procedure shall not appear within a DO CONCURRENT construct.
• 8436: Reference to this procedure is prohibited in the body of DO CONCURRENT statement.
• 8437: The type/rank signature for the arguments of this specific subroutine matches another specific subroutine that shares the same ASSIGNMENT generic binding.
• 8438: The INTENT declaration is incorrect for this dummy argument of the specific procedure in an ASSIGNMENT generic binding.
• 8439: The fortran standard does not allow OPTIONAL arguments of a specific procedure in an ASSIGNMENT generic binding.
• 8440: The Fortran standard requires an explicit INTENT(OUT) or INTENT(INOUT) for the first dummy argument of a subroutine in an ASSIGNMENT generic binding.
• 8441: The Fortran standard does not allow OPTIONAL arguments of a specific procedure in an OPERATOR generic binding.
• 8442: The INTENT declaration is incorrect for this dummy argument of a specific procedure in an OPERATOR generic binding.
• 8443: This generic type bound procedure reference has two or more specific procedures with the same type/rank/keyword signature.
• 8444: The specific subroutines in an ASSIGNMENT generic binding must have exactly two dummy arguments.
• 8445: The OPERATOR generic binding may not be specified for functions with no arguments or for functions with more than two arguments.
• 8446: A specific procedure must be a subroutine for an ASSIGNMENT generic binding.
• 8447: A specific procedure must be a function for an OPERATOR generic binding.
• 8448: An explicit INTENT(IN) declaration is expected for this dummy argument of a specific procedure in an OPERATOR generic binding.
• 8449: The type/rank/keyword signature for this specific procedure matches another specific procedure that shares the same generic binding name.
• 8450: The type/rank signature for this specific function and its arguments matches another specific function that shares the same OPERATOR generic binding.
• 8451: For the Gw.dEe edit descriptor, e may not be specified if w is zero.
• 8452: REAL(KIND=16) and COMPLEX(KIND=32) are treated the same as REAL(KIND=8) and COMPLEX(KIND=16).
• 8453: Unlimited-format-item is *(format-item-list). Format-item in list must not be empty
• 8454: STAT= may not appear more than once in an image control statements.
• 8455: ERRMSG= may not appear more than once in an image control statements.
• 8456: Only STAT= and ERRMSG= are allowed as specifiers in a SYNC ALL, SYNC IMAGES, or SYNC MEMORY statements.
• 8457: A reference to an image control statement must not appear within a DO CONCURRENT construct.
• 8458: A pure subprogram must not contain an image control statements.
• 8459: An image-set must be scalar or of rank one.
• 8460: An END CRITICAL statement exists without an associated CRITICAL statement.
• 8461: An unterminated block exists before an END CRITICAL statement.
• 8462: A CYCLE statement in a critical-construct that transfers control outside the critical-construct is not permitted.
• 8463: An EXIT statement in a critical-construct that transfers control outside the critical-construct is not permitted.
• 8464: The block of a critical-construct shall not contain a RETURN statement.
• 8465: The block of a critical-construct shall not contain an image control statement.
• 8466: A statement that branches from the block of a critical-construct to outside the critical-construct is not permitted.
• 8467: An image-set value must be positive.
• 8468: The BIND statement may specify the BIND attribute only for variables and common blocks.
• 8469: This derived type component is not a procedure and cannot be called.
• 8470: Unsupported target.
• 8471: This expression must be a scalar of integer type.
• 8472: Duplicate modifier.
• 8473: The OMP OFFLOAD directive must be followed by one of the OpenMP* directives PARALLEL, PARALLEL SECTIONS, or PARALLEL DO.
• 8474: A data component whose type has a coarray ultimate component must be a nonpointer nonallocatable scalar.
• 8475: An entity whose type has a coarray ultimate component must be a nonpointer nonallocatable scalar.
• 8476: An entity whose type has a coarray ultimate component must not be a coarray.
• 8477: If a coarray-spec appears, the component must not be of type C_PTR or C_FUNPTR.
• 8478: A named variable of type LOCK_TYPE or a named variable with a noncoarray sub-component of type LOCK TYPE must be a coarray.
• 8479: A lock variable or a variable with a subobject of type LOCK TYPE shall not appear in this definition context.
• 8480: A lock-variable must be of type LOCK TYPE.
• 8481: A variable with BIND(C) attribute cannot have either the ALLOCATABLE or the POINTER attribute.
• 8482: A variable with BIND(C) attribute cannot be a deffered shape array.
• 8483: A variable with BIND(C) attribute cannot be a coarray.
• 8484: The argument to STORAGE_SIZE is invalid.
• 8485: There is no matching specific function for this type bound generic function reference.
• 8486: There is no matching specific subroutine for this type bound generic subroutine call.
• 8487: The definition of a function that returns a procedure pointer is not yet supported.
• 8488: This syntax is invalid; the procedure name is required in procedure binding statement after '=>'.
• 8489: A GENERIC binding is permitted only within the type bound procedure part of a derived type.
• 8490: Transfer of control to the interior of this block from outside the block is prohibited.
• 8491: A branch within a DO CONCURRENT construct shall not have a branch target that is outside the construct.
• 8492: This directive is ignored due to current command line options.
• 8493: Only STAT= and ERRMSG= are allowed as specifiers in the UNLOCK statement.
• 8494: Only STAT=, ERRMSG= and ACQUIRED_LOCK= are allowed as specifiers in the LOCK statement.
• 8495: ACQUIRED_LOCK= may not appear more than once in the LOCK statement.
• 8496: A use associated object that has the PROTECTED attribute shall not appear as a lock-variable in the LOCK statement.
• 8497: Illegal use of a procedure name in an expression, possibly a function call missing parenthesis.
• 8498: An EXTERNAL procedure name must not appear in an input/output item list.
• 8499: The procedure has a dummy argument that is polymorphic. Required explicit interface is missing from original source.

Back to All Intel Fortran Compiler Diagnostics

• 8500: The coarrays are not supported in Fortran xx standard.
• 8501: The CODIMENSION attribute has incorrect syntax.
• 8502: The procedure has a result that is an array. Required explicit interface is missing from original source.
• 8503: The procedure has a result that is a pointer or is allocatable. Required explicit interface is missing from original source.
• 8504: The procedure has a result that has a nonassumed type parameter value that is not an initialization expression. Required explicit interface is missing from original source.
• 8505: TARGET or IF specifier is already defined in the directive.
• 8506: TARGET is not specified in the directive.
• 8507: ALLOC_IF or FREE_IF modifier can be specified for arrays or for a pointer or an allocatable scalar
• 8508: The syntax is incorrect, an ac-value expression is expected in this context.
• 8509: Designator for image selector is missed.
• 8510: If an allocate-coarray-spec is specified then the allocate-object must be an allocatable coarray.
• 8511: If the allocate-object is an allocatable coarray then an allocate-coarray-spec must be specified.
• 8512: The corank of an allocate-coarray-spec differs from the corank of the allocatable coarray object.
• 8513: The syntax of an allocate-coarray-spec is incorrect: either '*' or 'lower-bound-expr : *' is expected in this context.
• 8514: An allocate-coarray-spec in an ALLOCATE statement is incorrect.
• 8515: If generic name is the same as derived type name all of the procedures in the interface block must be functions.
• 8516: Coarray declarations are not allowed when the -coarray compiler option is not specified.
• 8517: Coarray declarations are not allowed when the /Qcoarray compiler option is not specified.
• 8518: Value of CONCURRENCY_SAFE attribute must be either PROFITABLE of COST(count).
• 8519: Value of COST must be positive integer below 65535.
• 8520: An array dummy argument of a BIND(C) procedure must be an explicit shape or assumed size array.
• 8521: A dummy argument of a BIND(C) procedure cannot be a coarray.
• 8522: A result variable of a BIND(C) procedure cannot have either the ALLOCATABLE or the POINTER attribute.
• 8523: A result variable of a BIND(C) procedure cannot be an array.
• 8524: The syntax of this data pointer assignment is incorrect: either 'bound spec' or 'bound remapping' is expected in this context.
• 8525: The syntax of this data pointer assignment is incorrect: the bound remapping list cannot contain a bound spec.
• 8526: The syntax of this data pointer assignment is incorrect: the bound spec list cannot contain a bound remapping.
• 8527: If a bound remapping list is specified, data target must be simply contiguous or of rank one.
• 8528: The data pointer assignment with a bound spec list is an extension of Standard Fxx.
• 8529: The data pointer assignment with a bound remapping list is an extension of Standard Fxx.
• 8530: If a bound spec list is specified, the ranks of data pointer object and data target must be the same.
• 8531: A left hand side of intrinsic assignment statement must be a variable.
• 8532: A character dummy argument with length other than 1 is not interoperable.
• 8533: A dummy argument of a BIND(C) procedure cannot have either the ALLOCATABLE or the POINTER attribute.
• 8534: Nested OFFLOAD directives are not allowed
• 8535: A procedure called in an OFFLOAD region must have the OFFLOAD:TARGET attribute.
• 8536: A variables used in an OFFLOAD region must not have type bound procedures.
• 8537: A global variable used in an OFFLOAD region must have the OFFLOAD:TARGET attribute.
• 8538: Assumed size variables cannot be used in an OFFLOAD region without length specifier.
• 8539: The PROTECTED attribute may be specified only for procedure pointers or variables.
• 8540: A use associated procedure pointer that has the PROTECTED attribute shall not appear in a pointer association context.
• 8541: Not yet implemented: type containing ALLOCATABLE field of same type. Use POINTER instead.
• 8542: A value for a parent component can be specified only with a component keyword.
• 8543: If the actual argument is a coindexed object, a pointer dummy argument is not allowed.
• 8544: An allocatable coarray dummy argument must correspond to an allocatable coarray actual argument.
• 8545: A variable used in an OFFLOAD region must not be of derived type with pointer or allocatable components.
• 8546: A local allocatable co-array in a recursive procedure is not yet supported
• 8547: The OFFLOAD directive must be followed by one of the OpenMP PARALLEL directives, a CALL statement, or an assignment statement where the right-hand side is only a function invocation.
• 8548: In an OpenMP* ATOMIC capture-statement, the lhs and rhs variables may not be the same
• 8549: In an OpenMP* ATOMIC write-statement, the rhs expression may not access the lhs variable
• 8550: An OpenMP* ATOMIC capture-statement is expected
• 8551: In an OpenMP* ATOMIC CAPTURE construct, the rhs of the capture-statement should be the same as the lhs of the update-statement
• 8552: The OpenMP* END ATOMIC directive for this OpenMP* ATOMIC directive block is either missing or misplaced
• 8553: A procedure called by a procedure with the OFFLOAD:TARGET attribute must have the OFFLOAD:TARGET attribute.
• 8554: The value of expression for OFFLOAD ALIGN must be a power of 2.
• 8555: A constant is not allowed in IN/OUT/INOUT clauses of an OFFLOAD directive.
• 8556: If the actual argument is a coindexed scalar, the corresponding dummy argument shall be scalar.
• 8557: Invalid clause for the DEC$ ATTRIBUTES VECTOR directive
• 8558: Only one procedure name is allowed.
• 8559: Not a valid processor name
• 8560: Vectorlength must be 2, 4, 8, 16, or 32.
• 8561: Not a valid dummy argument
• 8562: A step must be an integer literal constant or dummy argument.
• 8563: Only one value is allowed.
• 8564: Procedure name for the DEC$ ATTRIBUTES VECTOR directive must be the enclosing procedure or the procedure immediately following the directive.
• 8565: A global variable within a procedure with the OFFLOAD:TARGET attribute must have the OFFLOAD:TARGET attribute
• 8566: A variable step must be a dummy argument specified in a SCALAR clause.
• 8567: A type-declaration statement is not permitted after CONTAINS in a derived type declaration.
• 8568: The passed-object dummy argument can not have the VALUE attribute.
• 8569: A constant is not allowed in IN/OUT clauses of an OFFLOAD_TRANSFER directive.
• 8570: This expression must be a scalar variable of integer type.
• 8571: The target of a pointer shall not be a coindexed object.
• 8572: The DIM argument to LCOBOUND/UCOBOUND cannot be an optional dummy argument.
• 8573: Keyword 'OFFLOAD_ATTRIBUTE_TARGET' expected.
• 8574: A procedure-name in a generic interface block must be a nonintrinsic procedure that has an explicit interface.
• 8575: A derived type with the BIND attribute shall not have a type bound procedure part.
• 8576: ENTRY statement is an obsolescent feature in Fortran xx.
• 8577: The scale factor (k) and number of fractional digits (d) do not have the allowed combination of either -d < k < 0 or 0 < k < d+2. Expect asterisks as output.
• 8578: Multiple VECTORLENGTH/VECTORLENGTHFOR clauses specified.
• 8579: Not a valid data type for the VECTORLENGTHFOR clause.
• 8580: There is an unterminated OFFLOAD BEGIN TARGET directive block
• 8581: An OFFLOAD BEGIN directive block starts in one F95 block and ends in another.
• 8582: An END OFFLOAD directive occurred when there is no OFFLOAD BEGIN directive block pending
• 8583: COARRAY argument of ATOMIC_DEFINE/ATOMIC_REF intrinsic subroutine shall be a coarray.
• 8584: This symbol has multiply declared DEC$ ATTRIBUTES CVF attribute.
• 8585: This symbol has the illegal combination of DEC$ ATTRIBUTES CVF and DEFAULT specified.
• 8586: Implicit type is given to allow out-of-order declaration. Non-standard extension.
• 8587: WAIT specifier is already defined in the directive.
• 8588: SIGNAL specifier is already defined in the directive.
• 8589: Fortran xx specifies that if a bound remapping list is specified, data target must be of rank one.
• 8590: The DEC$ ATTRIBUTES directive on this platform does not support the CVF attribute.
• 8591: A variable must only be specified in one of the PRIVATE/LINEAR/REDUCTION/FIRSTPRIVATE/LASTPRIVATE SIMD clauses.
• 8592: Within a SIMD region, a DO-loop control-variable must not be specified in a PRIVATE/REDUCTION/FIRSTPRIVATE/LASTPRIVATE SIMD clause.
• 8593: Subobjects are not allowed in this SIMD clause; a named variable must be specified.
• 8594: A GENERIC type bound procedure name can not be overridden with a specific type bound procedure name in an extended type.
• 8595: A specification function cannot have a dummy procedure argument.
• 8596: SIGNAL clause requires an explicit device number in the TARGET clause.
• 8597: WAIT clause requires an explicit device number in the TARGET clause.
• 8598: A specific type bound procedure with the same name is already associated with this GENERIC type bound procedure.
• 8599: The OFFLOAD_TRANSFER directive can not have both IN and OUT clauses.
• 8600: The WAIT clause is not specified in the OFFLOAD_WAIT directive.
• 8601: The OFFLOAD_WAIT directive requires an explicit device number in the TARGET clause.
• 8602: A Cray pointee used in an OFFLOAD region must not be of derived type with pointer or allocatable components.
• 8603: A Cray pointer/pointee used in an OFFLOAD region must be explicitly specified in an IN/OUT/INOUT/NOCOPY clause.
• 8604: This expression is not allowed in copyin/copyout clauses of an OFFLOAD directive.
• 8605: A Cray pointee of derived type specified in in/out clauses cannot be an adjustable array.
• 8606: An adjustable array Cray pointee specified in in/out clauses requires a length modifier.
• 8607: The procedure interface for the type bound procedure is not yet available.
• 8608: A PARAMETER constant is not allowed in INTO modifier of an OFFLOAD directive.
• 8609: The shapes of the array expressions of source and destination objects do not conform.
• 8610: The structure types of source and destination objects cannot be different.
• 8611: The data types of source and destination objects must be the same.
• 8612: Only one identifier is allowed when the INTO modifier is used.
• 8613: Intrinsic NULL() must have the MOLD argument if it is an actual argument corresponding to a dummy argument with assumed type parameters.
• 8614: Intrinsic NULL() is passed as actual argument to a non-pointer, non-allocatable, non-optional dummy argument.
• 8615: Intrinsic NULL() is passed as actual argument. An explicit interface specifying that the corresponding dummy is pointer, allocatable or optional is required.
• 8616: A host associated variable used in an OFFLOAD region must have the SAVE and OFFLOAD:TARGET attributes.
• 8617: An array section used in IN/OUT/INOUT clause of an OFFLOAD directive must be contiguous.
• 8618: A PARAMETER constant is not allowed in the ALLOC modifier of an OFFLOAD directive.
• 8619: Only one identifier is allowed when the ALLOC modifier is used.
• 8620: The variable used in the INTO and ALLOC modifiers in an IN clause of the OFFLOAD directive must be the same variable.
• 8621: The variable used in the ALLOC modifier must be the same as the base variable in the IN/OUT/INOUT/NOCOPY clause of the OFFLOAD directive.
• 8622: An array section used in the ALLOC modifier of an OFFLOAD directive must be contiguous.
• 8623: The result variable of an interoperable function must itself be interoperable; character length must be 1
• 8624: The result variable of an interoperable function must itself be interoperable; derived type must be declared with BIND(C).
• 8625: In a derived type, only allocatable and pointer fields can be specified with a DEC$ ATTRIBUTES ALIGN attribute.
• 8626: The DEC$ ATTRIBUTES ALIGN attribute cannot specify a field in the parent type.
• 8627: The dummy argument used in an OFFLOAD region has the INTENT(IN) attribute; therefore it must be explicitly specified in an IN or NOCOPY clause.
• 8628: SUBMODULE is not yet supported.
• 8629: MANDATORY specifier already appears in the offload directive.
• 8630: The asynchronous offload directive can not be optional.
• 8631: OPTIONAL specifier already appears in the offload directive.
• 8632: The MANDATORY and OPTIONAL specifiers must not appear in the same offload directive.
• 8633: STATUS specifier already appears in the offload directive.
• 8634: STATUS specifier expression must be a scalar variable of the derived type.
• 8635: A DEC$ FMA or DEC$ NOFMA directive must not appear in a module specification-part.
• 8636: The specific subroutines in a formatted defined I/O must have exactly six dummy arguments.
• 8637: The specific subroutines in an unformatted defined I/O must have exactly four dummy arguments.
• 8638: The type/rank signature for arguments of this specific subroutine is identical to another specific subroutine that shares the same defined I/O.
• 8639: The type/rank of this dummy argument to a defined I/O procedure does not follow the standard specified interface.
• 8640: The INTENT attribute of this dummy argument to a defined I/O procedure does not follow the standard specified interface.
• 8641: A specific procedure associated with a defined I/O generic spec cannot have OPTIONAL arguments.
• 8642: A specific procedure must be a subroutine for a defined I/O.
• 8643: Multiple SAFELEN clauses are not allowed in an OpenMP* directive.
• 8644: SAFELEN operand must be a constant positive integer expression.
• 8645: ALIGNMENT operand must be a constant positive integer expression.
• 8646: STEP operand must be a constant positive integer expression.
• 8647: This symbol appears more than once in an ALIGNED clause[s] for a single OpenMP* directive.
• 8648: This symbol appears more than once in a LINEAR clause[s] for a single OpenMP* directive.
• 8649: No OpenMP* construct can appear in a SIMD region.
• 8650: The dummy argument received by value cannot be used as a tag in SIGNAL or WAIT specifiers.
• 8651: The OpenMP* SIMD directives require perfectly nested loops: no code may appear before or after the loops being collapsed.
• 8652: LINEAR list-item must be of type INTEGER.
• 8653: Invalid clause for the OpenMP* DECLARE SIMD directive.
• 8654: SIMDLEN length must be 2, 4, 8, 16, or 32.
• 8655: An OpenMP* DECLARE SIMD directive can not contain both INBRANCH and NOTINBRANCH clauses.
• 8656: An ATTRIBUTES VECTOR directive can not contain both MASK and NOMASK clauses.
• 8657: Multiple SIMDLEN clauses specified.
• 8658: An argument can appear in at most one UNIFORM or LINEAR clause.
• 8659: The argument of the ALLOCATED intrinsic can not be an array element.
• 8660: A variable used in an OFFLOAD region with length modifier must be a whole array reference.
• 8661: Only one DEVICE clause can be specified on this OpenMP* directive.
• 8662: A procedure called in an OpenMP* TARGET region must have the DECLARE TARGET attribute.
• 8663: A global variable used in an OpenMP* TARGET region must have the DECLARE TARGET MIRROR attribute.

• Diagnostics 5000-5499
• Diagnostics 5500-5999
• Diagnostics 6000-6499
• Diagnostics 6500-6999
• Diagnostics 7000-7499
• Diagnostics 7500-7999
• Diagnostics 8000-8499
• Diagnostics 8500-8999
• Diagnostics that do not have a number
  • fortcom: Fatal: There has been an internal compiler error
  • internal error: Please visit 'http://www.intel.com/software/products/support' for assistance.
  • catastrophic error: **Internal compiler error: segmentation violation signal raised**
  • catastrophic error: **Internal compiler error: internal abort** 

For diagnostics not listed here, please ask in our User Forums.

Back to All Intel Fortran Compiler Diagnostics

• 7500: The HPF ON/RESIDENT directives stack limit has been exceeded.
• 7501: The object/component/template must have non-zero rank.
• 7502: The rank of the object/component/template differs from the rank of the shadow-spec-list.
• 7503: The object/component/template has invalid shadow-specs.
• 7504: Non-negative integer value scalar initialization expression is required for the int-expr part of a shadow-spec.
• 7505: Multiple SHADOW attribute
• 7506: Invalid combined-decl.
• 7507: Direct or indirect specification function recursion is prohibited.
• 7508: A specification function must be a pure function.
• 7509: A specification function cannot be an internal function.
• 7510: An explicit interface is required for a specification function.
• 7511: Parenthesized home-expr is not a processors-element
• 7512: An ALLOCATE, DEALLOCATE, NULLIFY, or pointer assignment statement may interfere with other statements in the body of an HPF INDEPENDENT do-loop.
• 7513: Transfer of control to a branch target statement outside the body of a an HPF INDEPENDENT do-loop is prohibited.
• 7514: A STOP, ERROR STOP or PAUSE statement is prohibited in the body of an HPF INDEPENDENT do-loop.
• 7515: I/O operations in the body of an HPF INDEPENDENT do-loop may interfere with other operations.
• 7516: Invalid jump within a loop body controlled by the INDEPENDENT directive.
• 7517: Invalid jump into, out of, or within a loop body controlled by the INDEPENDENT directive.
• 7518: The same specific procedure appears more than once in the specific procedure list for a single generic-spec.
• 7519: This combined-decl must be a simple name since align-attribute-stuff is present on this combined-directive.
• 7520: A data-initialization-expr on a component-def-stmt was not in Fortran 90.
• 7521: Multiple PPD FIRSTPRIVATE option occurrences.
• 7522: Nesting of WHERE statements or constructs was not in Fortran 90.
• 7523: A where-construct-name was not part of Fortran 90.
• 7524: The masked-elsewhere-stmt was not part of Fortran 90.
• 7525: Specification functions were not part of Fortran 90.
• 7526: A generic-spec included on an end-interface-stmt is not standard Fortran 90.
• 7527: The NULL() intrinsic function was not part of Fortran 90.
• 7528: The CPU_TIME intrinsic function was not part of Fortran 90.
• 7529: The KIND parameter option for this intrinsic was not part of Fortran 90.
• 7530: The forall-construct was not part of Fortran 90.
• 7531: The forall-assignment-stmt was not part of Fortran 90.
• 7532: The number of arguments is incompatible with intrinsic procedure, assume 'external'.
• 7533: The object contains one or more misaligned fields.
• 7534: Since the length of this array object is not a multiple of its alignment and the size of the array is greater than 1, there are misaligned fields.
• 7535: A '*', or the BLOCK, CYCLIC, GEN_BLOCK, or INDIRECT keyword is expected.
• 7536: Multiple RANGE attribute
• 7537: The length of any range-attr-list must be equal to the rank of the ranger.
• 7538: Invalid range-attr.
• 7539: The ranger must have the DYNAMIC attribute, the INHERIT attribute, and no explicit DISTRIBUTE, or it must have been specified with a dist-format-clause of * in a DISTRIBUTE or combined directive.
• 7540: The ranger must not appear as an alignee in an ALIGN or REALIGN directive.
• 7541: Expected keyword MODEL, LANGUAGE, or EXTERNAL_NAME
• 7542: This intrinsic-spec-arg appears more than once.
• 7543: A char-initialization-expr is required.
• 7544: This char-initialization-expr must have the value 'HPF', 'C', 'F77', or 'FORTRAN'
• 7545: This char-initialization-expr must have the value 'GLOBAL', 'LOCAL', or 'SERIAL'
• 7546: An extrinsic-spec-arg language value of 'FORTRAN' can appear only in an interface-body.
• 7547: An extrinsic-spec-arg language value of 'C' can appear only in an interface-body.
• 7548: Keyword RESULT expected.
• 7549: A variable is required in this context.
• 7550: Fortran xx does not allow this data initialization.
• 7551: A dummy argument with the VALUE attribute cannot be optional.
• 7552: No assumed-size arrays in LASTLOCAL options clauses.
• 7553: This keyword is invalid for this HPF library procedure reference.
• 7554: No assumed-size arrays in LOCAL options clauses.
• 7555: This HPF library procedure reference contains too few arguments.
• 7556: This HPF library procedure reference contains too many arguments.
• 7557: This HPF library procedure reference is missing a required argument.
• 7558: Standard Fxx requires a double precision real type.
• 7559: Fortran xx requires that the type parameter and kind type parameter of the actual argument match the dummy argument; the actual has been converted to the type and kind type of the dummy.
• 7560: Identifier is expected between the slashes.
• 7561: The val in 'ALIGN=val' should be an integer ranging from 0 through 4; defaulting to 4.
• 7562: This statement is not permitted within a derived-type-def unless the derived type is a sequenced type.
• 7563: This derived type must be a sequenced type when appearing in this context.
• 7564: This RECORD structure is not permitted as a component of a derived-type-def since the derived-type is not a sequence type.
• 7565: A CHARACTER literal or a concatenation of CHARACTER literals is required for the first argument.
• 7566: A RETURN or EXIT statement is not legal in a DO loop associated with a parallel directive.
• 7567: pointee required in this context.
• 7568: Multiple 'CDEC$ RESTRICT' declaration for this pointee.
• 7569: This object appears as both an inheritee in an INHERIT directive and a distributee in a DISTRIBUTE/REDISTRIBUTE directive.
• 7570: This object appears as both an inheritee in an INHERIT directive and a alignee in an ALIGN/REALIGN directive.
• 7571: CDEC$ RESTRICT attribute can not be applied to a host associated pointee.
• 7572: There is no blank COMMON for this scoping unit.
• 7573: A block-data-name must be specified if extrinsic-prefix is specified.
• 7574: An internal procedure must be of the same extrinsic kind as its host..
• 7575: A module procedure must be of the same extrinsic kind as its host..
• 7576: An extrinsic-spec-arg language value of 'F77' can appear only in an interface-body.
• 7577: The attributes MAP_TO, LAYOUT, and/or PASS_BY may be specified only for dummy arguments within a scoping unit of an extrinsic type for which these attributes have been explicitly defined.
• 7578: More than one MAP_TO binding.
• 7579: More than one LAYOUT binding.
• 7580: More than one PASS_BY binding.
• 7581: A variable-name is required in this context.
• 7582: A variable-name is required in this context.
• 7583: A variable-name or a structure-component, where the rightmost part-ref is a name, is required in this context.
• 7584: A structure-component is not yet supported in this context.
• 7585: A variable that occurs as a reduction-variable must be of intrinsic type; it may not be of type CHARACTER.
• 7586: A variable that occurs as a reduction-variable may not appear in a new-clause in the same independent-directive.
• 7587: A variable that occurs as a reduction-variable may not appear in a new_clause of different INDEPENDENT directive in the same DO range.
• 7588: A variable that occurs as a reduction-variable may not appear in a reduction_clause of a different INDEPENDENT directive in the same DO range.
• 7589: Not a valid value for the char-expr in this connect-spec.
• 7590: Not a valid value for the char-expr in this io-control-spec.
• 7591: A PPD parallel loop must not be a DO WHILE loop.
• 7592: A PPD parallel loop must not be a DO forever loop.
• 7593: A DO WHILE loop must not follow a DEC loop optimization directive.
• 7594: A DO forever loop must not follow a DEC loop optimization directive.
• 7595: In an align-target that is a structure-component, every part-ref except the rightmost must be scalar (rank zero).
• 7596: The use of a TYPE(type-name) statement when there is an '%FILL' entity-decl is not valid and/or supported. Use RECORD/type-name/ instead.
• 7597: Both low-width and high-width must be present in a shadow-spec if the COLON option is used.
• 7598: This attr-spec is not valid and/or supported when an '%FILL' appears as an entity-decl of a type-declaration-stmt.
• 7599: A procedure name as an actual argument must not be the name of a generic name (R1214.4).
• 7600: A procedure name as an actual argument must not be the name of an internal procedure (R1214.4).
• 7601: Fxx standard does not allow an internal procedure to be an actual argument procedure name. (R1214.4).
• 7602: Not a derived-type variable.
• 7603: A structure-component is not permitted as an alignee in an ALIGN directive.
• 7604: Mapping to a processor subset is not [yet] supported.
• 7605: Invalid dist-target.
• 7606: Multiple SUBSET attribute and/or directive declaration.
• 7607: This object appears as a ranger and must have the DYNAMIC or INHERIT attr or be specified with a DISTRIBUTE dist-format-clause of *.
• 7608: This template appears as a ranger and must have the DYNAMIC attribute or be specified with a DISTRIBUTE dist-format-clause of *.
• 7609: If an ID= specifier is present then an ASYNCHRONOUS= specifier with the value YES shall be present.
• 7610: If and ASYNCHRONOUS specifier is present, the REC= specifier shall appear, a format shall not appear, and a namelist-group-name shall not appear.
• 7611: If an ASYNCHRONOUS specifier is present, then no function reference may appear in an expression anywhere in the data transfer statement.
• 7612: The ID= and PENDING= specifiers shall not appear in an INQUIRE statement if the FILE= specifier is present.
• 7613: If an ID= specifier is present then a PENDING= specifier shall be present.
• 7614: A wait-spec-list shall contain exactly one UNIT= specifier, exactly one ID= specifier, and at most one of each of the other specifiers.
• 7615: PPD (parallel processing) directives shall not appear in the same program unit with HPF directives when the -wsf switch is used.
• 7616: SMP optimizations are not permitted when compiling for one node; SMP optimizations have been disabled.
• 7617: This host associated object appears in a 'defining' context in a PURE procedure or in an internal procedure contained in a PURE procedure.
• 7618: In an elemental subprogram, a dummy argument, or a subobject thereof, shall not appear in a specification-expr except as the argument to certain inquiry functions.
• 7620: An EXIT statement is not legal in a DO loop associated with a an OpenMP* DO directive.
• 7621: The data type of the variable is not defined for the operator or intrinsic specified on the OpenMP* REDUCTION clause.
• 7622: Misplaced part of an OpenMP* parallel directive.
• 7623: An OpenMP* parallel loop must not be a DO WHILE loop.
• 7624: OpenMP* directives shall not appear in the same program unit with HPF directives when the -wsf switch is used.
• 7625: FORALL index variable hides non-scalar variable, it is prohibited by Fortran standard
• 7626: An OpenMP* directive block starts in one F95 block and ends in another.
• 7627: An OpenMP* directive occurred when there are no PPD block parallel-directives pending.
• 7628: This OpenMP* END directive does not match the OpenMP* block directive at the top of the stack.
• 7629: The name on the OpenMP* END CRITICAL does not match the name on the corresponding OpenMP* CRITICAL directive.
• 7630: This statement or directive is not permitted within the body of an OpenMP* SECTION of an OpenMP* SECTIONS directive or OpenMP* PARALLEL SECTIONS directive.
• 7631: This statement or directive is not permitted within the body of an OpenMP* MASTER/END MASTER block.
• 7632: This statement or directive is not permitted within the body of an OpenMP* ORDERED?END ORDERED block.
• 7633: A $OMP THREADPRIVATE directive references a non-existent common block.
• 7634: Names on the $OMP THREADPRIVATE directive must be enclosed in slashes.
• 7635: OMP SECTION directive is required.
• 7636: This statement or directive is not permitted within the body of an OpenMP* SINGLE directive
• 7637: An OpenMP* SECTION directive must appear lexically within an OpenMP* SECTIONS or OpenMP* PARALLEL SECTIONS directive.
• 7638: This OpenMP* work sharing construct is not lexically enclosed within a parallel region.
• 7639: This OpenMP* synchronization construct is not lexically enclosed within a parallel region.
• 7640: Multiple $OMP THREADPRIVATE declaration.
• 7641: Blank common shall not appear on an OpenMP* THREADPRIVATE directive.
• 7642: This name has not been defined and shall not be used in an OpenMP* THREADPRIVATE directive.
• 7643: Only one sequence directive with no association-name-list is permitted in the same scoping unit.
• 7644: The statement or directive following this OpenMP* directive is incorrect.
• 7645: Use of DEC$ ATTRIBUTES directive with module names is accepted, but has no effect.
• 7646: A store statement is expected in an OpenMP* ATOMIC construct.
• 7647: A align_target may not be an EQUIVALENCEd object.
• 7648: A alignee may not be an EQUIVALENCEd object.
• 7649: A distributee may not be an EQUIVALENCEd object.
• 7650: The Fxx standard says that this SAVE statement is invalid since there is an occurrence of another SAVE statement (or attribute) in the same scoping unit.
• 7651: The Fxx standard says that this SAVE statement is invalid since there is an occurrence of a SAVE statement with an omitted save-entity-list in the same scoping unit.
• 7652: The Fxx standard says that the SAVE attribute is invalid since there is an occurrence of a SAVE statement with an omitted save-entity-list in the same scoping unit.
• 7653: There are unterminated OpenMP* directive block[s].
• 7654: When the RUNTIME schedule type is specified, it is illegal to specify a chunk in the SCHEDULE or AUTO clause of an OpenMP* directive.
• 7655: A variable is required in this OpenMP* context.
• 7656: Subobjects are not allowed in this OpenMP* clause; a named variable must be specified.
• 7657: When a named common block is declared in an OpenMP* PRIVATE, FIRSTPRIVATE, or LASTPRIVATE clause, none of its constituent variables may be declared in another OpenMP* scope attribute.
• 7658: It is illegal for a constituent variable of a THREADPRIVATE common block to appear in any OpenMP* clause other than a COPYIN clause.
• 7659: An assumed sized array cannot be specified in an OpenMP* PRIVATE, FIRSTPRIVATE, LASTPRIVATE, COPYPRIVATE, or REDUCTION clause.
• 7660: An assumed shape array cannot be specified in an OpenMP* PRIVATE, FIRSTPRIVATE, or LASTPRIVATE clause.
• 7661: A pointee is not permitted in an OpenMP* PRIVATE, SHARED, FIRSTPRIVATE, LASTPRIVATE, or REDUCTION clause
• 7662: An integer pointer is not permitted in an OpenMP* REDUCTION clause.
• 7663: Blank common may not be specified in an OpenMP* context.
• 7664: It is illegal for a THREADPRIVATE common block to appear in any OpenMP* clause other than a COPYIN clause.
• 7665: The OpenMP* REDUCTION clause intrinsic must be MAX, MIN, IAND, IOR, or IEOR.
• 7666: The OpenMP* REDUCTION clause operator must be +, *, -, .AND., .OR., .EQV., or .NEQV..
• 7667: This statement or directive is not permitted within the body of an OpenMP* CRITICAL directive block.
• 7668: Common block names are not allowed for the DEC$ ATTRIBUTES ARRAY_VISUALIZER specifier.
• 7669: Common block names are not allowed for the DEC$ ATTRIBUTES NO_ARG_CHECK specifier.
• 7670: This symbol has multiply declared DEC$ ATTRIBUTES ARRAY_VISUALIZER attribute.
• 7671: This symbol has multiply declared DEC$ ATTRIBUTES NO_ARG_CHECK attribute.
• 7672: This DEC$ ATTRIBUTES directive can be used only with scalar or array objects that have the Fxx POINTER or ALLOCATABLE attributes; this DEC$ ATTRIBUTE will be ignored.
• 7673: The DEC$ ATTRIBUTES NO_ARG_CHECK directive shall appear only in an interface block or module procedure.
• 7674: The DEC$ ATTRIBUTES NO_ARG_CHECK declaration shall not be used for an elemental or pure procedure; the NO_ARG_CHECK declaration will be ignored.
• 7675: The NO_ARG_CHECK attribute may not be used in defined operators or defined assignments.
• 7676: Standard Fxx requires an explicit INTENT(OUT) or INTENT(INOUT) for a generic ASSIGNMENT procedure.
• 7677: This label has been branched to from outside this PPD or OpenMP* block.
• 7678: It is illegal to branch out of this OpenMP* block.
• 7679: It is illegal to branch out of this PPD block.
• 7680: This symbol appears more than once in PRIVATE clause[s] for a single OpenMP* directive
• 7681: This symbol appears more than once in FIRSTPRIVATE clause[s] for a single OpenMP* directive
• 7682: This symbol appears more than once in LASTPRIVATE clause[s] for a single OpenMP* directive
• 7683: This symbol appears more than once in SHARED clause[s] for a single OpenMP* directive
• 7684: This symbol appears more than once in REDUCTION clause[s] for a single OpenMP* directive
• 7685: An asterisk, i.e., '*', dummy argument is not supported for a specific-subroutine associated with a generic-name.
• 7686: The specific procedure associated with the current generic-spec cannot have an asterisk, i.e., '*', dummy argument.
• 7687: An alternate return (i.e., '*') dummy argument is not permitted when there are dummy arguments preceding it that have the OPTIONAL attribute.
• 7688: The '.' separator should not be used for dat-refs of this object; use the separator '%' instead.
• 7689: Only one DEFAULT clause can be specified on this PPD directive.
• 7690: This symbol appears more than once in PRIVATE clause[s] for a single PPD directive
• 7691: This symbol appears more than once in FIRSTPRIVATE clause[s] for a single PPD directive
• 7692: This symbol appears more than once in LASTPRIVATE clause[s] for a single PPD directive
• 7693: This symbol appears more than once in SHARED clause[s] for a single PPD directive
• 7694: This symbol appears more than once in REDUCTION clause[s] for a single PPD directive
• 7695: An entity cannot appear explicitly in more than one clause per directive except that an entity can be specified in both a FIRSTPRIVATE and LASTPRIVATE clause.
• 7696: Since the DEFAULT(PRIVATE) is specified for the parallel region, this PPD clause is not permitted on the work-sharing directive.
• 7697: This entity has already been privatized in the parallel region and cannot be privatized again by this PPD work-sharing directive.
• 7698: When a named common block is declared in a PPD PRIVATE, FIRSTPRIVATE, or LASTPRIVATE clause, none of its constituent variables may be declared in another OpenMP* scope attribute.
• 7699: Since the PPD DEFAULT(NONE) clause applies, the PRIVATE, SHARED, REDUCTION, FIRSTPRIVATE, or LASTPRIVATE must be explicitly specified.
• 7700: If the pointer-object (leftside) has the INHERIT attribute, the target (rightside) must be mapped.
• 7701: If the pointer-object (leftside) is not mapped, then the target (rightside) shall not be mapped and shall not have the INHERIT attribute.
• 7702: If the pointer-object (leftside) is mapped, the target (rightside) shall not have the INHERIT attribute, shall be mapped, and shall not be a section.
• 7703: Since the pointer-object (leftside) is a structure-component where the rightmost part-ref has the POINTER attribute, all part-refs to the left of the rightmost must not be mapped.
• 7704: Lead dollar sign is not permitted.
• 7705: Lead underscore is not permitted.
• 7706: Allowing an intrinsic procedure name to appear as an actual argument when the intrinsic procedure is not explicitly declared as INTRINSIC is not standard Fxx.
• 7707: Structure is empty.
• 7708: Record is empty.
• 7709: The symbolic name must be one of the intrinsic functions MAX, MIN, IAND, IOR, or IEOR.
• 7710: An array section having a vector subscript is not permitted if dummy argument has intent [IN]OUT
• 7711: An AUTOMATIC object cannot be initialized in a DATA statement.
• 7712: This variable has not been used.
• 7713: This statement function has not been used.
• 7714: Missing or improper statement following HPF ON directive.
• 7715: Replacing invalid structure constructor by integer 1
• 7716: This symbol has multiply declared DEC$ ATTRIBUTES DESCRIPTOR[32|64] attribute.
• 7717: DEC$ DESCRIPTOR/REFERENCE ATTRIBUTE valid only on interface dummy.
• 7718: DEC$ ATTRIBUTES ADDRESS64 object invalid for VMS
• 7719: DEC$ ATTRIBUTES ADDRESS64 object invalid for WNT
• 7720: DEC$ ATTRIBUTES ADDRESS64 object type had ALLOCATABLE or POINTER subobject
• 7721: This symbol has multiply declared DEC$ ATTRIBUTES ADDRESS64 declarations.
• 7722: RESULT name must not be same as ENTRY name
• 7723: RESULT name must not be same as FUNCTION name
• 7724: NAMELIST variable name not accessible
• 7725: An equivalence-object shall not have the TARGET attribute.
• 7726: Use of IMPLICIT statement with declaration warnings
• 7727: Recompiling Procedure
• 7728: Generating IFC profile node for program unit
• 7729: Reusing IFC profile node for program unit
• 7730: 'ALIGN=page'. Cannot specify alignment greater than 6 on WNT - using 4.
• 7731: This symbol has multiply declared DEC$ ATTRIBUTES DEFAULT attribute.
• 7732: CDEC$ ATTRIBUTES 'DEFAULT' applicable to procedures and common blocks only.
• 7733: This form of shadow specification deprecated; ignored. Use SHADOW directive.
• 7734: Rank mismatch in alignment directive.
• 7735: POINTER dummy argument must have INHERIT attribute.
• 7736: A POINTER dummy argument and its corresponding actual argument must both have mapping or must both have no mapping.
• 7737: FROM and TO arguments of JMVBITS must be of type INTEGER(4)
• 7738: FROM and TO arguments of KMVBITS must be of type INTEGER(8)
• 7739: An END TYPE statement is missing in a TYPE definition.
• 7740: With Default Real KIND = 4, arguments' data types are incompatible with intrinsic.
• 7741: With Default Real KIND = 8, arguments' data types are incompatible with intrinsic.
• 7742: With Default Double KIND = 8, arguments' data types are incompatible with intrinsic.
• 7743: With Default Double KIND = 16, arguments' data types are incompatible with intrinsic.
• 7744: With Default Integer KIND = 2, arguments' data types are incompatible with intrinsic.
• 7745: With Default Integer KIND = 4, arguments' data types are incompatible with intrinsic.
• 7746: With Default Integer KIND = 8, arguments' data types are incompatible with intrinsic.
• 7747: Invalid parameter expression.
• 7748: Since the physical representation of the result is shorter than that of SOURCE, the physical representation of the result is the leading part of SOURCE.
• 7749: Alignment of variable or array is inconsistent with its data type.
• 7750: Invalid edit descriptor node in format.
• 7751: ALLOCATABLE arrays or POINTER arrays may not be initialized.
• 7752: Internal compiler error. .
• 7753: Scalar pointer actual argument passed to dummy array is non-standard.
• 7754: Error occurred during /ANALYSIS_DATA processing. Please report the problem Compaq.
• 7755: Standard requires an EXTERNAL statement or an external interface for argument
• 7756: NUM_THREADS operand must be an integer expression
• 7757: NUMA clause and NUM_THREADS option may not both be present on an OMP directive
• 7758: NUMA clause and IF option may not both be present on an OMP directive
• 7759: FROM and TO arguments of MVBITS must have the same type and kind parameters
• 7760: This parameter has not been used
• 7761: Ignoring HPF directive. -ignore_hpf_dirs switch set
• 7762: With -wsf, -ignore_hpf_dirs switch is ignored
• 7763: Parameter not used.
• 7764: Parameter used.
• 7765: FATAL ERROR - conflict or recursive module USE
• 7766: The statement sequence is incomplete or incorrect
• 7767: An assumed size array cannot be passed as argument when dummy is an assumed shape array
• 7768: This operation on this data type is currently inaccurate.
• 7769: The RESIDENT/END RESIDENT directive is checked for syntactic and semantic correctness, but it is then ignored by the current HPF compiler.
• 7770: Page size is undefined on this platform.
• 7771: Name and type conflict; name is illegal.
• 7772: Complex*32 is not supported on this platform.
• 7773: COMPLEX(KIND=16) is not supported on this platform.
• 7774: Constants of this type may not be passed as actual arguments 'by value'.
• 7775: Placement of NAMELIST statement is non-standard.
• 7776: OPEN (FORM=BINARY) is not supported on VMS.
• 7777: This intrinsic has been deprecated.
• 7778: The ARRAY argument of the ALLOCATED inquiry intrinsic function shall be an allocatable array and not a cross-section.
• 7779: Argument to MIGRATE_NEXT_TOUCH or MIGRATE_NEXT_TOUCH_NOPRESERVE must be scalar-name, array-name or pointer-name.
• 7780: First/last address parameters to MIGRATE_TO_OMP_THREAD must not be sections.
• 7781: Section subscript in MIGRATE_NEXT_TOUCH or MIGRATE_NEXT_TOUCH_NOPRESERVE directive improper; follows non-section subscript(s).
• 7782: Section subscript in MIGRATE_NEXT_TOUCH or MIGRATE_NEXT_TOUCH_NOPRESERVE directive improper; has a non-unit stride, or section parameters involve expressions.
• 7783: A name that identifies a global entity is used to identify another global entity in the same program.
• 7784: Symbol in BLOCK DATA program unit is not in a COMMON block.
• 7785: 1785 - AVAILABLE FOR ERROR MESSAGE.
• 7786: Field width is not standard Fortran xx; is less than or equal to zero.
• 7787: With Default Real KIND = 16, arguments' data types are incompatible with intrinsic.
• 7788: With Default Double KIND = 16, arguments' data types are incompatible with intrinsic.
• 7789: HPF mappings applied to fields of derived types must be constants
• 7790: NUMA mappings applied to fields of derived types must be constants
• 7791: Only a dummy argument may have the DEC$ ATTRIBUTES directive ALLOW_NULL specifier.
• 7792: Only a dummy argument may have the DEC$ ATTRIBUTES directive IGNORE_LOC specifier.
• 7793: This symbol has multiply declared DEC$ ATTRIBUTES DECORATE attribute.
• 7794: Only a function or subroutine subprogram may have the DEC$ ATTRIBUTES directive DECORATE specifier.
• 7795: Common block names are not allowed for the DEC$ ATTRIBUTES [NO]MIXED_STR_LEN_ARG specifier.
• 7796: Only a function or subroutine subprogram may have the DEC$ ATTRIBUTES directive [NO]MIXED_STR_LEN_ARG specifier.
• 7797: Common block names are not allowed for the DEC$ ATTRIBUTES IGNORE_LOC specifier.
• 7798: Common block names are not allowed for the DEC$ ATTRIBUTES ALLOW_NULL specifier.
• 7799: %LOC is being stripped from argument which has REFERENCE and IGNORE_LOC attributes.
• 7800: An expression in the mapping directive for a derived type field is not constant.
• 7801: Integer pointers may not point to mapped objects.
• 7802: A non-sequential (element-granularity) distributee/alignee may not be an EQUIVALENCEd object.
• 7803: The NOSEQUENCE directive may not be specified for a component of a derived type which has the SEQUENCE attribute.
• 7804: Arrays in reduction clauses are not supported.
• 7805: Character expression not allowed where arithmetic expression required.
• 7806: Variable name, array reference or structure component reference required.
• 7807: The specification-part of a PURE subroutine subprogram must specify the intents of all dummy arguments except procedure arguments and arguments with the POINTER attribute.
• 7808: An assumed shape array (INTENT(IN)) may not have the ALLOCATABLE attribute.
• 7809: Standard Fortran xx requires that defined operators consist only of letters.
• 7810: The mask-expr on the masked-where-stmt does not conform with the mask-expr for the containing where.
• 7811: Error with derived type symbol whose definition contains a PRIVATE statement.
• 7812: Symbol/Name is improper in this context.
• 7813: ALLOW_NULL and REFERENCE attribute pair is disallowed with assumed shape arrays
• 7814: Properties of array are unknown. Possibly the result of a recursive specification.
• 7815: Use of symbol in specification expression for type parameter is non-standard.
• 7816: Invalid assignment to function result of external procedure.
• 7817: Overflow occurred while evaluating constant expression.
• 7818: This feature is not supported on this platform.
• 7819: It is non-standard to call an elemental procedure with an array having vector valued subscripts if the dummy argument has intent [IN]OUT.
• 7820: The val in 'ALIGN=val' must be an integer ranging from 0 through 12.
• 7821: The value of array bounds must be within 2**31-1 and -2**31.
• 7822: Variables containing ultimate allocatable array components are forbidden from appearing directly in input/output lists.
• 7823: Variables containing ultimate allocatable array components cannot appear in COMMON or EQUIVALENCE statements.
• 7824: POINTER and ALLOCATABLE attributes shall not both appear in the same component definition statement.
• 7825: An entity with the ALLOCATABLE attribute may not have the PARAMETER attribute.
• 7826: A data-i-do-object or a variable that appears as a data-stmt-object, shall not be of a derived type containing an allocatable array as an ultimate component.
• 7827: No Component of an initialization expression may have the ALLOCATABLE attribute
• 7828: The part-name to the right of a part-ref with nonzero rank has the ALLOCATABLE attribute (6.1.2).
• 7829: This expression cannot be evaluated.
• 7830: Multiple OMP NUM_THREADS clauses in a parallel region are not allowed
• 7831: List directed ENCODE/DECODE not supported
• 7832: Greater than 7 dimensions is non-standard
• 7833: Use of this function name is not valid in this context
• 7834: An automatic object must not have the SAVE attribute specified or implied by initialization.
• 7835: Record fields or array elements or sections of pointers are not themselves pointers.
• 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.
• 7837: Two or more accessible entities, other than generic interfaces, may have the same name only if the name is not used to refer to an entity in the scoping unit.
• 7838: A scalar default-integer variable is required in this context.
• 7839: In a case-value-range the range must be of the form low-value:high-value.
• 7840: A character string or Hollerith string is non-standard in this context.
• 7841: DLL IMPORT/EXPORT is not supported on this platform.
• 7842: Substring-range starting or ending point is not a scalar integer expression.
• 7843: No statements, including FORMAT and DATA statements, may appear between the SELECT CASE statement and the first CASE statement of a CASE construct.
• 7844: Invalid directive.
• 7845: An ENDOPTIONS directive occurred without a corresponding CDEC$ OPTIONS directive.
• 7846: It is not permissible to reference the value of an ac-implied-do variable in one of its limit expressions
• 7847: Allocatable fields of derived types is an extension of Standard Fxx.
• 7848: A non-intrinsic elemental procedure shall not be used as an actual argument
• 7849: The ELEMENTAL attribute of the associated actual procedure differs from the ELEMENTAL attribute of the dummy procedure.
• 7850: Intrinsic DIM argument shall not be an optional dummy argument.
• 7851: If dummy arg is allocatable, actual arg must be a whole array and not a section.
• 7852: The use of a scalar in a structure constructor for an allocatable array component is not allowed
• 7853: An assumed-size array shall not be written as a whole array reference except as an actual argument in a procedure reference for which the shape is not required.
• 7854: A parameter may not be declared as a pointer variable
• 7855: A DEC$ OMP SHARABLE directive references a non-existent common block.
• 7856: An entity cannot be both SHARABLE and THREADPRIVATE.
• 7857: Multiple DEC$ OMP SHARABLE declaration.
• 7858: Names on the DEC$ OMP SHARABLE directive must be enclosed in slashes.
• 7859: A SHARABLE or THREADPRIVATE entity is not permitted in a PRIVATE, FIRSTPRIVATE, LASTPRIVATE, SHARED or REDUCTION clause.
• 7860: An entity cannot appear explicitly in more than THREADPRIVATE or SHARABLE directive.
• 7861: This symbol has multiply declared DEC$ ATTRIBUTES ALIGN attribute.
• 7862: This symbol has multiply declared DEC$ ATTRIBUTES INLINE attribute.
• 7863: This symbol has multiply declared DEC$ ATTRIBUTES NOINLINE attribute.
• 7864: This symbol has multiply declared DEC$ ATTRIBUTES FORCEINLINE attribute.
• 7865: Improperly positioned OMP SECTION DIRECTIVE.
• 7866: The statement following this DEC loop optimization directive must be an iterative do-stmt, a vector assignment, an OMP pdo-directive, or an OMP parallel-do-directive.
• 7867: This directive is misplaced or not supported on this platform.
• 7868: A sharable directive may not appear in a BLOCKDATA program unit.
• 7869: Implicitly-declared variables may not be declared sharable.
• 7870: Formal arguments may not be declared sharable.
• 7871: Variables accessed via use association may not be declared sharable in the using program.
• 7872: An attempt has been made to DLLIMPORT or DLLEXPORT a non-existing COMMON block.
• 7873: Non-PURE intrinsic procedures may not be referenced in a PURE procedure
• 7874: An OpenMP* ORDERED directive can appear only in the dynamic extent of a DO or PARALLEL DO directive
• 7875: The INTENT(OUT) or INTENT(INOUT) specification is not valid for dummies of pure functions.
• 7876: If RESULT is not specified, it is non standard to treat the function-name as a function instead of as the result_variable
• 7877: This intrinsic is not supported on this platform
• 7878: Variables that appear on the FIRSTPRIVATE, LASTPRIVATE, and REDUCTION clauses on a work-sharing directive must have shared scope in the enclosing region
• 7879: Assumed-size arrays cannot be declared PRIVATE, FIRSTPRIVATE, LASTPRIVATE, or COPYPRIVATE.
• 7880: Variables in the COPYPRIVATE list must not appear in a PRIVATE or FIRSTPRIVATE clause for the SINGLE construct
• 7881: This module file was generated for a different platform or by an incompatible compiler or compiler release. It cannot be read.
• 7882: Missing end statement on this program unit.
• 7883: The standard requires that derived types be predefined.
• 7884: Use of a statement function in a specification expression is not allowed.
• 7885: If a component of a derived type is of a type declared to be private, either the derived type definition shall contain the PRIVATE statement or the derived type shall be private.
• 7886: UNIT and FILE arguments to OPEN and CLOSE statements must be scalars and not arrays
• 7887: Dynamic common disallowed in BLOCK DATA unit
• 7888: Initial data disallowed for dynamic common
• 7889: MS$ATTRIBUTES disallowed for dynamic common block
• 7890: MS$ATTRIBUTES disallowed for dynamic common variable
• 7891: Dynamic common not allowed in a module
• 7892: Procedure argument must be PURE
• 7893: Allocatable dummy arguments is an extension of Standard Fxx.
• 7894: Allocatable function results is an extension of Standard Fxx.
• 7895: The HINT, FAULT and EXCLUSIVE arguments must be compile time constants.
• 7896: The HINT argument has an invalid value. Must be 0,1,2 or 3
• 7897: A UNION may not contain an ALLOCATABLE component
• 7898: If an external or dummy procedure name is used as an actual argument, its interface shall be explicit or it shall be explicitly declared to have the EXTERNAL attribute
• 7899: Case cannot be reached, since low-value is greater than high-value
• 7900: Equivalenced objects may not be SHARABLE
• 7901: A character expression is expected as a format specifier
• 7902: The SAVE attribute may only be declared for objects in a subprogram
• 7903: A variable in a THREADPRIVATE directive must not be an element of a common block or be declared in an equivalence statement
• 7904: A variable in a SHARABLE directive must not be an element of a common block or be declared in an equivalence statement
• 7905: Non-standard array initialization. The shapes of the array expressions do not conform.
• 7906: Overflow occurred while calculating array size
• 7907: Overflow occurred while calculating common block size
• 7908: POINTER/POINTEE symbols have different visibility attributes
• 7909: A variable that appears in a THREADPRIVATE directive and is not declared in the scope of a module must have the SAVE attribute
• 7910: A variable may not exceed 2147483647 bytes
• 7911: Adding this variable to common-block-object-list causes the common block size to exceed the maximum of 2147483647 bytes.
• 7912: An explicit INTENT(OUT) declaration is expected for this dummy argument
• 7913: This function or subroutine name appeared illegally in a prior NAMELIST statement
• 7914: Alignment value too big, is greater than 16384
• 7915: A specification expression object must be a dummy argument, a COMMON block object, or an object accessible through host or use association - may be used in multiple contained procedures.
• 7916: OBJCOMMENT is not supported on this platform.
• 7917: The workshare construct SINGLE or SECTIONS is invalid in a PARALLELDO which must contain a single DO directive
• 7918: A RETURN statement is invalid as an exit from a parallel region
• 7919: The value was too small when converting to REAL(KIND=4); the result is zero.
• 7920: The value was too small when converting to REAL(KIND=4); the result is in the denormalized range.
• 7921: The value was too small when converting to REAL(KIND=8); the result is zero.
• 7922: The value was too small when converting to REAL(KIND=8); the result is in the denormalized range.
• 7923: The value was too small when converting to REAL(KIND=16); the result is zero.
• 7924: The value was too small when converting to REAL(KIND=16); the result is in the denormalized range.
• 7925: An interface-block in a subprogram shall not contain an interface-body for a procedure defined by that subprogram.
• 7926: This statement is not a valid OpenMP* ATOMIC update-statement.
• 7927: An OpenMP* WORKSHARE directive is not permitted in the dynamic extent of a CRITICAL, MASTER or ORDERED directive.
• 7928: An OpenMP* PARALLEL WORKSHARE directive is not permitted in the dynamic extent of a CRITICAL, MASTER or ORDERED directive.
• 7929: This statement or directive is not permitted within the body of an OpenMP* WORKSHARE directive
• 7930: The inquire by DIRECTORY= form of the INQUIRE statement requires an EXIST= specifier.
• 7931: An invalid specifier has been seen; the inquire by DIRECTORY= form of the INQUIRE statement only allows the EXIST= and DIRSPEC= specifiers.
• 7932: A DIRSPEC= specifier is only allowed with the inquire by DIRECTORY= form of the INQUIRE statement.
• 7933: For the INQUIRE statement, an inquire-spec-list must contain at least one FILE= specifier, one UNIT= specifier or one DIRECTORY= specifier.
• 7934: An INQUIRE statement must contain only one FILE= specifier, one UNIT= specifier or one DIRECTORY= specifier.
• 7935: A user defined function that is not an ELEMENTAL function is not allowed within an OpenMP* WORKSHARE or OpenMP* PARALLEL WORKSHARE block.
• 7936: This statement or directive is not permitted within the block of an OpenMP* WORKSHARE or OpenMP* PARALLEL WORKSHARE directive.
• 7937: The OPTIONAL attribute should not be used for arguments with the VALUE attribute.
• 7938: Character length argument mismatch.
• 7939: A scalar default-character variable is required in this context.
• 7940: The initialization shall not appear for this object name.
• 7941: A scalar default-logical variable is required in this context.
• 7942: Intrinsic SIZE argument shall not be an optional dummy argument.
• 7943: The val in 'ALIGN:val' must be a power of 2 value from 1 up to 4096 (2**12).
• 7944: The val in 'ALIGN:val' must be a power of 2 value from 1 up to 16384 (2**14).
• 7945: The val in 'ALIGN:val' must be a power of 2 value from 1 up to 128 (2**7).
• 7946: The val in 'ALIGN:val' must be a power of 2 value.
• 7947: A variable format expression shell be a scalar numeric expression.
• 7948: In this initialization, there are more variables than values assigned to the variables.
• 7949: All internal subprograms in a pure subprogram shall be pure.
• 7950: Procedure name in MODULE PROCEDURE statement must be the name of accessible module procedure.
• 7951: The STATUS= specifier has the value SCRATCH, the FILE= specifier will be ignored in the OPEN statement.
• 7952: The TYPE= specifier has the value SCRATCH, the FILE= specifier will be ignored in the OPEN statement.
• 7953: Standard Fortran requires that within a scoping unit, two procedures that have the same generic name shall both be subroutines or both be functions.
• 7954: The floating invalid condition was detected while evaluating this operation; the result is a NaN.
• 7955: A variable is required in a MEMREF_CONTROL or PREFETCH directive.
• 7956: The 'distance' argument has an invalid value. Must be greater than (>) 0
• 7957: The 'locality' argument has an invalid value. Must be 1,2,3 or 4
• 7958: The 'latency' argument has an invalid value. Must be 1,2,3 or 4
• 7959: The 'SHAPE' argument of intrinsic function 'RESHAPE' shall be of type integer, rank one, and constant positive size less than 8.
• 7960: The floating overflow condition was detected while evaluating this operation; the result is an Infinity.
• 7961: This module file was not generated for IA64_WNT nor IA64_LINUX . It cannot be read by IA32 cross compiler
• 7962: A record or structure may not exceed 2147483647 bytes
• 7963: An OpenMP* DO directive is not permitted in a DO directive that binds to the same PARALLEL directive.
• 7964: An OpenMP* DO directive is not permitted in a WORKSHARE directive that binds to the same PARALLEL directive.
• 7965: An OpenMP* SECTIONS directive is not permitted in a SECTIONS directive that binds to the same PARALLEL directive.
• 7966: An OpenMP* SECTIONS directive is not permitted in a WORKSHARE directive that binds to the same PARALLEL directive.
• 7967: An OpenMP* SINGLE directive is not permitted in a SINGLE directive that binds to the same PARALLEL directive.
• 7968: An OpenMP* SINGLE directive is not permitted in a WORKSHARE directive that binds to the same PARALLEL directive.
• 7969: An OpenMP* WORKSHARE directive is not permitted in a DO directive that binds to the same PARALLEL directive.
• 7970: An OpenMP* WORKSHARE directive is not permitted in a SECTIONS directive that binds to the same PARALLEL directive.
• 7971: An OpenMP* WORKSHARE directive is not permitted in a SINGLE directive that binds to the same PARALLEL directive.
• 7972: An OpenMP* WORKSHARE directive is not permitted in a WORKSHARE directive that binds to the same PARALLEL directive.
• 7973: A numeric or LOGICAL data type is required in this context.
• 7974: An elemental intrinsic function here must be of type integer and each argument must be an initialization expression of type integer or character.
• 7975: This syntax is invalid; the keywords IN, OUT, or INOUT must appear only once when using the INTENT attribute.
• 7976: An allocatable dummy argument may only be argument associated with an allocatable actual argument.
• 7977: The type of the function reference does not match the type of the function definition.
• 7978: Required interface for passing assumed shape array is missing from original source
• 7979: A VOLATILE statement cannot specify a procedure, function result or namelist group
• 7980: The DO directive to which the ordered section binds does not have the ORDERED clause specified.
• 7981: The assignment statement following $OMP ATOMIC directive must be an intrinsic assignment statement.
• 7982: Variables in the COPYPRIVATE list must be PRIVATE in the enclosing parallel region.
• 7983: The storage extent of the dummy argument exceeds that of the actual argument.
• 7984: A CHARACTER function name must not be declared with an asterisk type-param-value (i.e., (LEN=*)) if the function is part of an interface-body. No interface block will be generated.
• 7985: A COMMON block data object may not have the PROTECTED attribute.
• 7986: A use associated object that has the PROTECTED attribute shall not appear in a variable definition context.
• 7987: This symbol has multiple PROTECTED statement/attribute declarations which is not allowed.
• 7988: A use associated object that has the PROTECTED attribute shall not appear as a stat-variable in an allocate or a deallocate statement.
• 7989: A use associated object that has the PROTECTED attribute shall not appear as an internal-file-variable in a write statement.
• 7990: A use associated object that has the PROTECTED attribute shall not appear as an IOSTAT=, SIZE=, IOMSG= specifier in an input/output statement.
• 7991: A use associated object that has the PROTECTED attribute shall not appear as a definable variable in an INQUIRE statement.
• 7992: A use associated object that has the PROTECTED attribute shall not appear as a variable-name in a namelist-stmt if the namelist-group-name appears in a NML= specifier in a read-stmt.
• 7993: A use associated object that has the PROTECTED attribute shall not appear as an actual argument if the associated dummy argument has the INTENT(OUT) or INTENT(INOUT) attribute.
• 7994: A use associated object that has the PROTECTED attribute shall not appear as a target in a pointer-assignment-stmt.
• 7995: DEC$ ATTRIBUTES DLLIMPORT or DLLEXPORT data may not be equivalenced.
• 7996: DEC$ ATTRIBUTES DLLIMPORT or DLLEXPORT data may not be LOCAL.
• 7997: Privatization (via DEFAULT(PRIVATE) or DEFAULT(FIRSTPRIVATE) clause) of an assumed size array is not allowed.
• 7998: The fxx standard requires that the argument of the MOVE_ALLOC intrinsic subroutine shall be an allocatable array.
• 7999: The FROM argument of a MOVE_ALLOC reference must have the INTENT(INOUT) attribute; the TO argument must have the INTENT(OUT).

Hi All,

I want to have my popup windows centered over their parent window regardless of which monitor the parent window is currently on. The method I have found from Web searching depends on functions such as MonitorFromWindow, part of the MSDN Multiple Display Monitors Reference. But I can't find a way to link to these functions. For example:

integer*4, parameter:: MONITOR_DEFAULTNEAREST = 2
interface
   integer*4 function MonitorFromWindow(hWnd,Flags)
      integer*4,intent(in):: hWnd,Flags
   end function
end interface

hMonitor = MonitorFromWindow(hWndParent,MONITOR_DEFAULTNEAREST)

The linker gives me "Unresolved external symbol ...", etc

Any suggestions?

Many thanks in advance,

Mike

dear all：

ruining in docker  container

kernel：

CentOS release 6.5 (Final)  2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

vendor_id       : GenuineIntel
cpu family      : 6
model           : 62
model name      : Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz
stepping        : 4
cpu MHz         : 2599.825
cache size      : 20480 KB
physical id     : 0
siblings        : 16
core id         : 6
cpu cores       : 8
apicid          : 13
initial apicid  : 13
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms
bogomips        : 5199.65
clflush size    : 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
 

painc messages

The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /export/servers/nginx/sbin/nginx
[Thread debugging using libthread_db enabled]
init sucess
[New Thread 0x7ffff7fa5700 (LWP 7301)]
[New Thread 0x7ffff1699700 (LWP 7302)]
[New Thread 0x7ffff1298700 (LWP 7303)]
[New Thread 0x7ffff0e97700 (LWP 7304)]
[New Thread 0x7ffff0a96700 (LWP 7305)]
[New Thread 0x7ffff0695700 (LWP 7306)]
*** glibc detected *** /export/servers/nginx/sbin/nginx: double free or corruption (!prev): 0x0000000000923f80 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x75e66)[0x7ffff5623e66]
/lib64/libc.so.6(+0x789b3)[0x7ffff56269b3]
/usr/lib/libGraphicsMagick.so.3(+0x133a7c)[0x7ffff70f5a7c]
/usr/lib/libGraphicsMagick.so.3(+0x13bbeb)[0x7ffff70fdbeb]
/opt/intel/composer_xe_2013_sp1.2.144/ipp/../compiler/lib/intel64/libiomp5.so(__kmp_invoke_microtask+0x93)[0x7ffff511c233]
======= Memory map: ========
00400000-00509000 r-xp 00000000 fd:04 918887                             /export/servers/nginx/sbin/nginx
00708000-0071a000 rw-p 00108000 fd:04 918887                             /export/servers/nginx/sbin/nginx
0071a000-00968000 rw-p 00000000 00:00 0                                  [heap]
7fffd4000000-7fffd4021000 rw-p 00000000 00:00 0
7fffd4021000-7fffd8000000 ---p 00000000 00:00 0
7fffdc000000-7fffdc021000 rw-p 00000000 00:00 0
7fffdc021000-7fffe0000000 ---p 00000000 00:00 0
7fffe0000000-7fffe0021000 rw-p 00000000 00:00 0
7fffe0021000-7fffe4000000 ---p 00000000 00:00 0
7fffe4000000-7fffe4021000 rw-p 00000000 00:00 0
7fffe4021000-7fffe8000000 ---p 00000000 00:00 0
7fffe8000000-7fffe8021000 rw-p 00000000 00:00 0
7fffe8021000-7fffec000000 ---p 00000000 00:00 0
7fffec000000-7fffec021000 rw-p 00000000 00:00 0
7fffec021000-7ffff0000000 ---p 00000000 00:00 0
7ffff0295000-7ffff0296000 ---p 00000000 00:00 0
7ffff0296000-7ffff0696000 rw-p 00000000 00:00 0
7ffff0696000-7ffff0697000 ---p 00000000 00:00 0
7ffff0697000-7ffff0a97000 rw-p 00000000 00:00 0
7ffff0a97000-7ffff0a98000 ---p 00000000 00:00 0
7ffff0a98000-7ffff0e98000 rw-p 00000000 00:00 0
7ffff0e98000-7ffff0e99000 ---p 00000000 00:00 0
7ffff0e99000-7ffff1299000 rw-p 00000000 00:00 0
7ffff1299000-7ffff129a000 ---p 00000000 00:00 0
7ffff129a000-7ffff329a000 rw-p 00000000 00:00 0
7ffff329a000-7ffff32a6000 r-xp 00000000 fd:04 524365                     /lib64/libnss_files-2.12.so
7ffff32a6000-7ffff34a6000 ---p 0000c000 fd:04 524365                     /lib64/libnss_files-2.12.so
7ffff34a6000-7ffff34a7000 r--p 0000c000 fd:04 524365                     /lib64/libnss_files-2.12.so
7ffff34a7000-7ffff34a8000 rw-p 0000d000 fd:04 524365                     /lib64/libnss_files-2.12.so
7ffff34a8000-7ffff34af000 r-xp 00000000 fd:04 524528                     /lib64/librt-2.12.so
7ffff34af000-7ffff36ae000 ---p 00007000 fd:04 524528                     /lib64/librt-2.12.so
7ffff36ae000-7ffff36af000 r--p 00006000 fd:04 524528                     /lib64/librt-2.12.so
7ffff36af000-7ffff36b0000 rw-p 00007000 fd:04 524528                     /lib64/librt-2.12.so
7ffff36b0000-7ffff36ef000 r-xp 00000000 fd:04 657779                     /usr/lib64/libjpeg.so.62.0.0
7ffff36ef000-7ffff38ef000 ---p 0003f000 fd:04 657779                     /usr/lib64/libjpeg.so.62.0.0
7ffff38ef000-7ffff38f0000 rw-p 0003f000 fd:04 657779                     /usr/lib64/libjpeg.so.62.0.0
7ffff38f0000-7ffff3900000 rw-p 00000000 00:00 0
7ffff3900000-7ffff3952000 r-xp 00000000 fd:04 1323448                    /opt/intel/composer_xe_2013_sp1.2.144/compiler/lib/intel64/libintlc.so.5
7ffff3952000-7ffff3b52000 ---p 00052000 fd:04 1323448                    /opt/intel/composer_xe_2013_sp1.2.144/compiler/lib/intel64/libintlc.so.5
7ffff3b52000-7ffff3b55000 rw-p 00052000 fd:04 1323448                    /opt/intel/composer_xe_2013_sp1.2.144/compiler/lib/intel64/libintlc.so.5
7ffff3b55000-7ffff3b56000 rw-p 00000000 00:00 0
7ffff3b56000-7ffff3b5b000 r-xp 00000000 fd:04 1323378                    /opt/intel/composer_xe_2013_sp1.2.144/compiler/lib/intel64/libirng.so
7ffff3b5b000-7ffff3d5b000 ---p 00005000 fd:04 1323378                    /opt/intel/composer_xe_2013_sp1.2.144/compiler/lib/intel64/libirng.so
7ffff3d5b000-7ffff3d5d000 rw-p 00005000 fd:04 1323378                    /opt/intel/composer_xe_2013_sp1.2.144/compiler/lib/intel64/libirng.so
7ffff3d5d000-7ffff4721000 r-xp 00000000 fd:04 1323415                    /opt/intel/composer_xe_2013_sp1.2.144/compiler/lib/intel64/libsvml.so
7ffff4721000-7ffff4921000 ---p 009c4000 fd:04 1323415                    /opt/intel/composer_xe_2013_sp1.2.144/compiler/lib/intel64/libsvml.so
7ffff4921000-7ffff4958000 rw-p 009c4000 fd:04 1323415                    /opt/intel/composer_xe_2013_sp1.2.144/compiler/lib/intel64/libsvml.so
7ffff4958000-7ffff4bd9000 r-xp 00000000 fd:04 1323461                    /opt/intel/composer_xe_2013_sp1.2.144/compiler/lib/intel64/libimf.so
7ffff4bd9000-7ffff4dd8000 ---p 00281000 fd:04 1323461                    /opt/intel/composer_xe_2013_sp1.2.144/compiler/lib/intel64/libimf.so
7ffff4dd8000-7ffff4e1b000 rw-p 00280000 fd:04 1323461                    /opt/intel/composer_xe_2013_sp1.2.144/compiler/lib/intel64/libimf.so
7ffff4e1b000-7ffff4e8c000 r-xp 00000000 fd:04 524525                     /lib64/libfreebl3.so
7ffff4e8c000-7ffff508b000 ---p 00071000 fd:04 524525                     /lib64/libfreebl3.so
7ffff508b000-7ffff508d000 r--p 00070000 fd:04 524525                     /lib64/libfreebl3.so
7ffff508d000-7ffff508e000 rw-p 00072000 fd:04 524525                     /lib64/libfreebl3.so
7ffff508e000-7ffff5092000 rw-p 00000000 00:00 0
7ffff5092000-7ffff5177000 r-xp 00000000 fd:04 1323455                    /opt/intel/composer_xe_2013_sp1.2.144/compiler/lib/intel64/libiomp5.so
7ffff5177000-7ffff5377000 ---p 000e5000 fd:04 1323455                    /opt/intel/composer_xe_2013_sp1.2.144/compiler/lib/intel64/libiomp5.so
7ffff5377000-7ffff5382000 rw-p 000e5000 fd:04 1323455                    /opt/intel/composer_xe_2013_sp1.2.144/compiler/lib/intel64/libiomp5.so
7ffff5382000-7ffff53aa000 rw-p 00000000 00:00 0
7ffff53aa000-7ffff53ac000 r-xp 00000000 fd:04 524519                     /lib64/libdl-2.12.so
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7ffff0695700 (LWP 7306)]
0x00007ffff55e0625 in raise () from /lib64/libc.so.6
(gdb) bt
#0  0x00007ffff55e0625 in raise () from /lib64/libc.so.6
#1  0x00007ffff55e1e05 in abort () from /lib64/libc.so.6
#2  0x00007ffff561e537 in __libc_message () from /lib64/libc.so.6
#3  0x00007ffff5623e66 in malloc_printerr () from /lib64/libc.so.6
#4  0x00007ffff56269b3 in _int_free () from /lib64/libc.so.6
#5  0x00007ffff70f5a7c in DestroyEdge (polygon_info=0x1c32, mid=3.2252605360516574e-319, fill=7306, fill_rule=6, x=-1, y=0,
    stroke_opacity=0x1) at magick/render.c:790
#6  GetPixelOpacity (polygon_info=0x1c32, mid=3.2252605360516574e-319, fill=7306, fill_rule=6, x=-1, y=0, stroke_opacity=0x1)
    at magick/render.c:3180
#7  0x00007ffff70fdbeb in L_DrawPolygonPrimitive_3546__par_loop1_2_1200 () at magick/render.c:3594
#8  0x00007ffff511c233 in L_kmp_invoke_pass_parms ()
   from /opt/intel/composer_xe_2013_sp1.2.144/ipp/../compiler/lib/intel64/libiomp5.so
#9  0x00007fffffff5098 in ?? ()
#10 0x00007fffffff5038 in ?? ()
#11 0x00007fffffff5090 in ?? ()
#12 0x00007fffffff5048 in ?? ()
#13 0x00007fffffff5078 in ?? ()
#14 0x00007fffffff5074 in ?? ()
#15 0x00007fffffff5028 in ?? ()
#16 0x00007fffffff5030 in ?? ()
#17 0x00007fffffff5010 in ?? ()
#18 0x00007fffffff5018 in ?? ()
#19 0x00007fffffffb688 in ?? ()
#20 0x00007ffff752403c in .2.23_2__kmpc_chunk_pack_.27 () from /usr/lib/libGraphicsMagick.so.3

Hi!

I'm researching on barrier algorithms using SIMD instructions and I'm trying to deeply understand the different versions included in the RTL.

I've noticed that there is a new barrier algorithm (hierarchical) since the last time I had a look.

Where could I find a further description of them? Could someone from Intel provides me with further information?

Thank you in advance.

Kind regards.

  Hi,

  I am running a coarray fortran application with intel fortran compiler ifort (IFORT) 13.0.1 20121010, and after some transfers between images, the code crashes with the error:

Fatal error in MPI_Win_create: Other MPI error, error stack:
MPI_Win_create(153)...........: MPI_Win_create(base=0x23ec030, size=8224, disp_unit=1, MPI_INFO_NULL, comm=0x84000000, win=0x2c92650) failed
MPID_Win_create(37)...........: 
MPIDI_Win_create(92)..........: 
MPIR_Comm_dup_impl(55)........: 
MPIR_Comm_copy(1070)..........: 
MPIR_Get_contextid(543).......: 
MPIR_Get_contextid_sparse(834): Too many communicators

It seems to me that the compiler is translating each sync images/daa transfer into a different MPI communicators, and therefore the program runs very fast out of communicators.

The code crashes after a fixed number of calls to a subroutine that reads:

  subroutine copybnd_su2_id(U,latt, id, ieo)

    type (SU2_field), intent (inout) :: U
    type (lattice), intent (in)  :: latt
    integer, intent (in) :: id, ieo

    integer :: imx, j, ifc, kt, ipr, isrc, iofs
    complex (kind=DPC), allocatable :: zbuf(:,:)[:], zloc(:,:)

    iofs = 0
    imx = maxval(latt%iface(:))/2+1
    allocate(zbuf(imx,2)[*], zloc(imx,2))

    ...

Any ideas about how to overcome this issue?

I have traditionally done my solution builds at the command line using devenv.exe.  However this doesn't use all my cores.  I did a search online and saw that msbuild does just this and with /m:8 uses all of my 8 cores.  However it only builds the (C++) vcxproj projects in my solution not the vfproj ones.  Are Fortran projects not supported under msbuild?  If not how can I use all my 8 cores at the command line?  I can do this using the Visual Studio environment, so presumably I can at the command line.

I'm writing UMAT with the help of fortran to be used with ABAQUS input file. I just wonder why I input value such as 0.38 in the input file and write in the output of the UMAT it will be 0. Anyone knows how to solve this? Thank you.

Regards,

Vicky

Hi Guys,

I am compiling a fortran library with a C++ DLL. I am using the Multi-threaded DLL option in my fortran project. My C++ part is also Multi-threaded. My problem is that if I look at the dependency of the resulting DLL, I see a dependency to LIBIFCORERT instead of LIBIFCOREMD or I see both fortran runtime libs as dependency...

What am-I missing ?

Thank you

Philippe

I found a few places in my legacy code where the obsolete VAX "parallel directive" feature exists, e.g.:

CPAR$ SOME_TEXT

Inasmuch as this is in a FORTRAN 77 fixed-format file, can I assume that this is simply ignored by Intel Fortran as if it is a comment?

Thanks,
JayB 

I have installed Microsoft Visual Studio Professional 2013 and Intel Parellel Studio XE Composer Edition for Fortran Windows ( downloaded file w_fcompex_all_jp_2013_sp1.4.237.exe ).   In attempting to build a solution from a .vfproj which has been successfully by others in our group, I get "rc.exe not found".  Where should "rc.exe" be?  I tried re-installing Intel Fortran and it did not work.  Does "rc.exe" come from Visual Studio?  Also, others in our group who can successfully build the .vfproj do not even have a "rc.exe" on their hard drive.  Thanks

                istat=-99 ! initialise  istat as it might not be assigned and then gives an uninitalised var failure.
                CALL EXECUTE_COMMAND_LINE("fred.exe",WAIT=.true.,EXITSTAT=istat)

And from the help>>>

exitstat

(Inout; optional) Must be a scalar of type integer. If the command is executed synchronously, exitstat is assigned the value of the processor-dependent exit status of the executed command. Otherwise, the value of exitstat is unchanged.

If istat is not pre-initialised and if a synchronous command fails to run (e.g. not found) istat is returned uninitialised and a "check uninit" runtime error occurs. I can see a number of different argument on this but the normal expectation of a intrinsic with a return status is for the return status to always be set.

I think a note advising initialisation by be helpful as setting a return status that is unconnected with the command being run might also cause confusion.

Hi,

I tried to access a variable and check its value during debug in VS 2012 with Intel 2015 update 1

However, it is not possible, stating "undefined variable xxx" but some other variables can be seen. So some works, some not.

However, the same variable can be accessed by the same code in VS 2008 with Intel 2013 in another colleague's computer.

May I know why? Is there some options I can change?

Thanks!

Hi,

I am running a mpi CFD code in my sch's cluster using 100 cpu.

Due to my program's structure, this is the max cpu I can use. At the same time, due to the number of grids using in my code, I am reaching the available memory limit.

The code ran and hang at a spot. After debugging, I found that it hangs in one of the subroutines. In this subroutines, I have to update the values of different variables across all cpu using mpi.

There are some local array which I need to create. If I declare them using:

subroutine mpi_var_...

real(8) :: var_ksta(row_num*size_x*size_y), ...

... 

end subroutine 

The code hangs.

However, if I do this:

subroutine mpi_var_...

real(8), allocatable :: var_ksta(:) ...

allocate (var_ksta(row_num*size_x*size_y)

...

deallocate (var_ksta, STAT=status(1))

end subroutine

The code works. So how different is memory allocated in these 2 situations?

If I am not tied down by memory limit, is the 1st subroutine faster or the same as the 2nd one (with allocation / deallocation slowing it down)?

Thanks!

I am planning on parallelizing a hotspot in a project. And I would like to know your opinion between the performance evaluation between parallel for, omp single followed by task and intel TBB task_list, under ideal conditions where number of threads are equal to computation items and when computation are much greater than available threads to see scheduling overhead(in order to evaluate the most efficient scheduler). I will also, be writing some sample test programs to evaluate myself but I also wanted to know if anybody had previously made these evaluations.

Thanks in advance.