Intel Fortran Compiler Diagnostics 6500-6999

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.