Lower bound expression of the DO statement has an
error. The format of the DO statement is DO s [,] i = e1, e2
[,e3]. The expressions "e1," "e2," and
"e3" are each an INTEGER, REAL, or DOUBLE PRECISION
expression. In this statement, "e3" has a syntax error.
MAP statement must be preceded by a UNION
statement. The MAP statement was scanned during a parse state
where KAP was not expecting a MAP declaration type for the present
structure declaration block.
MAP statement must be used inside a STRUCTURE declaration
block.
MAP/ENDMAP statements must have at least one
field-declaration.
Missing operand. An operator has been found that
does not have enough operands.
Multiple declaration of variable. Variable has
been declared in previous type declaration statement.
Multiple initialization of the same variable is not
allowed. Variable has been initialized previously.
Name enclosed in slashes "#1" is not the name of
a named COMMON block. In a save statement, a COMMON block name
is specified by enclosing it in slashes. The name found between the
slashes has not been used as the name of a COMMON block previously in
this compilation unit.
Name is not a legal external identifier. The
indicated name is not a legal external name for the target language. It
either has too many characters or contains a character that is not
allowed in external names.
Name was previously used in a conflicting way. The
name was used previously in a declaration statement, an expression, or
other manner such that the current use is no longer legal. For example,
a name may not be dimensioned more than once.
Negation cannot be applied to an expression of type
"#1". Negation "-" cannot be applied to
expressions of the given type.
Nested loops with same variable "#1".
The index variable for nested loops should not be the same.
Number of items in the variable list is not the same as in
the constant list. The number of items specified in the
variable list must be the same number in its corresponding constant
list.
Number of places in edit descriptor must not exceed field
width. The number of places (m) required in Iw.m edit
descriptor must not exceed the field width (w).
Octal constant contains characters that are not
0-7. An octal constant may contain only the digits
0,1,2,3,4,5,6, or 7. The specified constant contained one or more
digits that were 8 or 9.
Octal constant too long. Only 43 digits are
allowed. An octal constant can only be 128 bits long. The
specified constant contained more than 43 digits.
Only constants are allowed in this expression. The
indicated expression element is illegal in this context.
Only equality comparisons can be made on complex
values. Logical operators .GT., .GE., .LT., .LE. cannot be
applied to complex values.
Only formal parameters and constants are allowed in this
expression.
Only simple parameters and constants are allowed in this
expression. Only scalar variable parameters and constants are
allowed in this expression.
Operands are not conformable. The operands
involved must have the same number of array section selectors.
Operator was not expected here. An operator was
found in the wrong place.
Parameter U is required but was not found. The
letter U is required as the third parameter for DEFINE FILE.
Parallel constructs are not contained in the same statement
flow-control block. Currently, KAP only allows each Parallel
construct to be started and ended in the same statement flow-control
block.
Periods can only be used to form numbers or extended
operators/operands. A period was encountered, but it was not
part of a number or part of an extended operator/operand.
Preceding EQUIVALENCE group must have more than one
entry. A single name was specified inside an EQUIVALENCE
group. At least two names must be specified in each group.
Previous I/O control entry has already been
specified. Each type of I/O control entry can be specified at
most once. The I/O control entry that was specified just prior to the
current column had been specified earlier.
Previous I/O control entry may not be specified in this
type of I/O statement. Each type of I/O statement allows
certain I/O control entries to be specified. The I/O control entry that
was specified just prior to the current column may not be specified
with this I/O statement.
Range of first letters specified in this IMPLICIT statement
is invalid. An IMPLICIT statement must specify either a single
letter or two letters separated by a dash, with the first letter
preceding the second in the alphabet. The range of letters specified
must not overlap any other ranges specified in this or other IMPLICIT
statements.
Record name "#1" cannot be used in an EQUIVALENCE
statement.
Repetition factor must be greater than zero.
Repetition factors for repeatable format items must be greater than
zero.
Right parenthesis that matches this left parenthesis is
missing. The indicated left parenthesis has no corresponding
right parenthesis.
Right parenthesis was expected here but not found.
A right parenthesis was expected in the indicated column, but another
symbol was found instead.
Scalar expression expected. A scalar expression
was expected but not found, for example in the logical expression of an
if statement.
Scalar integer expression must follow the label list in a
computed GOTO. The format of a computed GOTO requires that an
integer expression follow the list of statement labels. This expression
can be an integer constant, an integer variable, an integer array
element, or any form of scalar integer expression.
Semicolon vector syntax not accepted by this
product. This product does not accept semicolon vector
notation. Use some other notation such as Fortran 8X triplets.
Shape mismatch: Shape of left side is "#1" and
shape of right side is not. The shape of the left and right
sides of an assignment statement must be the same or conformable. The
shape of the left side (mentioned in the message) and the shape of the
right side do not agree.
Size of hollerith constant exceeds remaining statement
length. A hollerith constant was specified with a length that
is longer than the number of characters that are left in the statement.
Statement contains too many continuation lines.
KAP expects a maximum number of continuation lines per statement. This
maximum is product-dependent. When the maximum is exceeded, no further
tokenization takes place until a noncontinuation line is encountered.
Statement is not any of the possible GOTO
statements. The syntax of this statement is so confused that
KAP could not decide what type of statement it is. It appears to be
some type of GOTO statement, but little else can be determined.
Statement label "#1" was referenced, but never
defined in this program unit.
Statement must occur earlier in the program unit.
The definition of the version of Fortran being accepted gives the
restrictions on statement ordering within a single compilation unit.
The statement being scanned violates this order requirement. Check the
Compaq Fortran user guide or Compaq Fortran reference
manual.
Statement unrecognizable as any known statement
type. The given statement contains errors that make it
impossible to tell what type of statement it was intended to be. The
keyword at the beginning of the statement (if any) did not match any of
the known statement keywords. The statement also did not contain any
equals signs at parenthesis nest level 0, necessary for the statement
to be an assignment statement. This error may be caused by incorrect
parenthesis nesting, or by a misspelled keyword.
String constant was not closed by end of
statement. A string constant was begun by an apostrophe or
double quote, but no trailing delimiter was encountered before the end
of statement was reached.
Structure name of a record is the same as the defining
STRUCTURE. A structure name of a record cannot be used within
the defining declaration for that structure name.
Structure references must be defined prior to use in a
RECORD statement.
Structure-name has been used previously in a STRUCTURE
declaration.
Structure-name is missing from the STRUCTURE
declaration. Structure names are required on the structure
declaration at the outermost level of nesting.
Substring denoted by this expression is not within declared
length of string. The starting position of a substring
specification must be at least 1, and the ending position must be at
most the length of the string.
Symbolic constant must be a simple scalar entity.
The name of a symbolic constant must not be dimensioned, or in any way
appear different than that of a scalar variable.
Symbolic constant must not be defined more than once in a
program unit. The symbolic constant that is defined to the
left of the current column has been either in an earlier PARAMETER
statement in this program unit, or in an earlier portion of this
PARAMETER statement. Each symbolic constant in a program unit can be
defined only once.
Text "#1" following a STOP or PAUSE is not an
integer or string constant. The format of the STOP statement
is STOP [n]. The format of the PAUSE statement is PAUSE [n]. In either
case, "n" must be either a string of not more than 5 digits
or a character constant.
The %FILL pseudo-name cannot be dimensioned.
The array "#1" has adjustable dimension and must
appear in dummy argument list. At least one dummy argument
list of the subprogram must contain the name of the adjustable array.
The field name "#1" has an illegal adjustable
dimension. Adjustable or assumed sized arrays and passed
length CHARACTER declarations are not allowed in field declarations.
The field-name has not been defined in the associated
structure.
The preceding parallel and/or synchronization
region/section is not closed. The present Parallel directive
was scanned or the end of the program was reached where KAP was
expecting a closing Parallel directive for the preceding parallel
region/section block.
This declaration type is not allowed in structure
declaration blocks. During the scanning process, a declaration
type has been detected within a STRUCTURE declaration block that is not
allowed.
This directive is not adjacent to the loop it applies
to. KAP recognizes directives in a file only if they are
placed immediately before the loop that they are to affect.
This Parallel directive should be inside a Parallel
PARALLEL REGION. Work-sharing or synchronization Parallel
constructs should be used inside a Parallel fork/join construct (that
is, a PARALLEL REGION).
Too many arguments in FUNCTION/SUBROUTINE. Some
products put restrictions on the number of arguments allowed in
SUBROUTINE/ FUNCTION.
Too many labels in computed GOTO. Some products
put restrictions on the number of labels allowed in a computed GOTO
statement.
Too many parameters are specified to this intrinsic
function. Too many parameters appear in the invocation of the
indicated intrinsic function. Check the intrinsic function and code the
correct number of parameters.
Transfer into IF or DO block from outside the IF or DO
block is prohibited. Transfer of control into an IF-block or
DO-block from outside the block is not allowed.
Type conversion not supported for this product.
This message is issued if the type conversion did not exist to type
cast the statement function expression to the type of the statement
function.
Unary operator has more than one operand. A unary
operator was found that has an operator on the left side.
Unexpected character. In processing a statement, a
character was encountered that was not allowed at the place it was
found. Check the syntax of the statement where the error occurred.
Unexpected symbol. The indicated symbol is not
legal at this point in the statement.
UNION statement must be used inside a STRUCTURE declaration
block.
UNION statement must not be preceded by a UNION
statement. The UNION statement was scanned during a parse
state where KAP was expecting a MAP declaration type for the present
structure declaration block.
Unknown I/O control entry begins at the current
column. An I/O control entry that is not in the table of all
possible I/O control entries begins at the current column. This I/O
control entry is not the first or second entry in this control list,
because those two can be positional (unit and format).
Unrecognized .xxx. operator. A token was
recognized as having the format of an extended operator/operand (period
identifier period), but the extended operator/operand was not in the
table of known extended operators/operands. Check the system Compaq
Fortran user guide.
Unsubscripted arrays not permitted in expressions and
assignment statements. An array name without a subscript is
not allowed in expressions and assignment statements.
Upper bound expression of the DO statement has an
error. The format of the DO statement is DO [,] i = e1, e2
[,e3]. The expressions "e1," "e2," and
"e3" are each an INTEGER, REAL, or DOUBLE PRECISION
expression. In this statement, "e2" has a syntax error.
Variable "#1" has no dimension bounds
specified. Variables declared in a dimension statement must
have at least one dimension bound, enclosed in parentheses, specified.
Variable "#1" must be explicitly typed.
IMPLICIT NONE and UNDEFINED ( for few dialects ) disables automatic
typing. All variables occurring within the scope of IMPLICIT NONE or
UNDEFINED must be explicitly typed.
Variable already occurred in a DATA statement. The
variable is declared after it has already been used in a data statement.
Variable list is missing from this list-directed I/O
statement. The comma after the format in a list-directed READ,
PRINT, or PUNCH statement was present, but the variable list following
the comma was missing.
Variable must be an array. The simple variable in
question is used in a context requiring an array.
Variable name "#1" is too long. The
given variable name is too long for the target language.
Variable name is required at this point. Only a
variable can be used at this point.
Variables from different COMMON blocks may not be
equivalenced. An EQUIVALENCE statement must not cause the
storage sequences of two different COMMON blocks in the same program
unit to be associated.
COMMON block /"#1"/ contains both character and
non-character data. If a character variable or character array
is in a COMMON block, all of the entities in that COMMON block must be
of type character.
Intrinsic function call could not be converted to the
target language. This intrinsic function call was to be
converted for output, but did not exist in the target language and had
no known equivalent (or generic) form. You must determine the correct
action to take.
Routine "#1" analyzed interprocedurally.
When optimizing the loop containing this call, IPA was performed on the
called routine.
Routine "#1" was inlined/IPAed. The call
to this routine was replaced by the body of the routine to enhance
optimization. The source of the subroutine or function is available
either in the same file or in a specified library.
Routine "#1" was not inlined/IPAed. Actual and
formal parameter counts differ. The number of formal
parameters in the definition of the program unit, in the same
compilation stream or in the library, differs from the number of actual
parameters at the call site.
Routine "#1" was not inlined/IPAed. Space
limitations exceeded. The inlining of subroutine or function
calls at this statement was not attempted due to limitations placed on
the amount of data structure space used in inline expansion.
Routine "#2" was not inlined/IPAed. COMMON block
"#1" item counts differ. The COMMON block mentioned
is defined in both the program unit being called and the calling
program unit. The number of separate entities in the two definitions do
not match.
Routine "#2" was not inlined/IPAed. COMMON block
item "#1" has a shape mismatch. The COMMON block
mentioned is defined in both the program unit being called and the
calling program unit. The entity mentioned has a different shape
(scalar or array) than its corresponding entity in the called program
unit.
Routine "#2" was not inlined/IPAed. COMMON block
item "#1" has a type mismatch. The COMMON block
mentioned is defined in both the program unit being called and the
calling program unit. The entity mentioned has a different type
(integer, logical, real, and so on) than its matching entity in the
called program unit.
Routine "#2" was not inlined/IPAed. External name
"#1" has unresolvable conflict. In the called and
calling routines, the definitions of an externally visible entity
cannot be reconciled. This may be an error in the program itself.
Routine "#2" was not inlined/IPAed. Non scalar
parameter "#1" is passed into scalar. The actual
parameter of a function/subroutine call differs in shape from the
corresponding formal parameter, that is scalar.
Routine "#2" was not inlined/IPAed. Parameter
"#1" is a nonarray passed into array. The actual
parameter of a call statement differs in shape from the corresponding
formal parameter, which is an array.
Routine "#2" was not inlined/IPAed. Parameter
"#1" cannot conform without linearizing. Before the
program unit is placed inline, the translation of formal parameters to
their actual equivalents must be made (a process called conformance).
First the scalars in the parameter list are matched, then the arrays
are examined to see what the proper translation is (the scalars are
done first because bounds of an array parameter are often passed as a
separate scalar). In this process, each dimension is compared, and a
translation is constructed that tries to keep each dimension of the
actual parameter separate. If this is not possible, the array
references (or a portion of them) must be linearized to do the
translation correctly. This is not desirable because the linearized
subscripts violate the bounds of the array reference, and the data
dependence tests used to optimize the program are compromised.
Routine "#2" was not inlined/IPAed. Parameter
"#1" has a class mismatch. Inline expansion or IPA
was aborted due to class mismatch between formal and actual parameters.
Routine "#2" was not inlined/IPAed. Parameter
"#1" has type mismatch. For inlining to work, the
types of the formal parameters and actual parameters must agree. Any
program unit called with parameters of the wrong type will get an
incorrect value unless assigned before any use in the call, and
assigned before the next use after the call.
Routine "#2" was not inlined/IPAed. Parameter
"#1" whole array does not conform. Inline expansion
or IPA was aborted because whole arrays do not conform.
Routine "#2" was not inlined/IPAed. The shape of
parameter "#1" is unknown. The shape of an actual
parameter to a call cannot be determined. It must be array, scalar, or
an intrinsic or external function call.
Dynamic array is referenced in the statement.
There is a reference to a dynamic array that may prevent translation.
Optimization from pass: "#1" is inhibited because
of data structure overflow. The given pass did not optimize
the entire program unit because the amount of storage required to do so
would exceed the capacity of internal data structures.
Note
It is possible for a given routine to be partially optimized by the
pass that issues this message.
Possible use of variable "#1" before its
definition. Live variable analysis was performed and a
possible use of the specified variable was found before any definition.
The optimizer may be acting (necessarily) conservatively and the
variable may not actually be used before any definition.
Two-version loop was created here. The loop cannot
be vectorized as-is because of possible data dependencies. An inserted
IF block eliminates this possibility, and the loop can be vectorized.
Bounds of this DO loop were changed because of
interchanging triangular loops. The indicated loop was one of
two or more triangular loops that were interchanged. The bounds were
modified so that the same index variable values would be covered by the
loops.
Condition from the IF statement at this line was assigned
to a temporary array. The condition from the IF statement that
was at the same line number as this statement was assigned to a
temporary array in order that the body of the IF could be split across
multiple loops.
Loop was distributed. This loop was broken up into
two or more loops to optimize one or more of the resulting loops.
Too many messages were issued for this compilation
unit. Either there were too many syntax errors, or the program
unit is too large for the vectorization message tables.
Data dependence analysis aborted due to insufficient
storage for graph arcs. Data dependence analysis was aborted
because of insufficient storage allocated for dependence graph arcs.
ELSE IF construct found. This loop was not
optimized because the target machine does not support optimization of
loops with ELSE IF constructs.
Exits found. This loop was not optimized because
it contains exits. The target machine does not support optimization of
loops with exits.
GOTO statement found. This loop was not optimized
because the target machine does not support optimization of loops with
GOTO statements.
Inner loop structure is too complex. This loop was
not optimized because the inner loop structure was too complex. This
could be because of a complex data dependence graph or because of a
complex flow graph structure.
Loop was asserted serial by directive. The present
loop was asserted serial by the use of a directive. Optimization was
not attempted for this loop.
Nested IFs found. This loop was not optimized
because the target machine does not support optimization of loops with
nested IFs.
No optimizable statements found. No optimizable
statements were found in this loop.
No parallelism detected. The optimizer could not
detect any parallelism in this loop.
Non-integer loop control variable found. This loop
was not optimized because of a non-integer loop control variable.
Changing the index variable appropriately may enable optimization of
the loop.
Non-optimizable intrinsic found. This loop was not
optimized because it contains a call to a nonoptimizable intrinsic
function or subroutine.
Non-optimizable operator found. This loop was not
optimized because it contains an operator that cannot be optimized.
Non-optimizable statement found. This loop was not
optimized because it contains one or more statements that cannot be
optimized safely.
Non-optimizable variable type found. This loop was
not optimized because of the presence of a nonoptimizable variable
type. The target machine does not support optimizations for variables
of this type.
Non-stride-1 references found. This loop was not
optimized because the target machine does not support optimization of
non-stride-1 loops.
Not an inner loop. This loop was not optimized
because the target machine does not support the optimization of
non-inner loops.
Optimization was disabled. The present loop was
not optimized because optimization had been disabled.
Prevented by reference(s) to variable
"#1". This loop was not optimized because of the
presence of the named variable. Restructuring of the code to simplify
references to this variable may enable further optimization.
Scalar mode determined best. No better execution
mode than scalar was found for this loop. Of all valid loop orderings
considered, this ordering was determined to be the best.
Statement with alternate returns found. This loop
was not optimized because of the presence of a statement with alternate
returns.
Too many dependence arcs. There are too many
dependence arcs for this loop. Increasing the value of
-arclimit may enable optimization of this loop.
Too many loop orderings. There are too many loop
orderings generated for this loop nest. Increasing the value of
-limit may enable optimization of this loop.
Unoptimizable call to "#1" found. This
loop was not optimized because of the presence of a call to the given
function or subroutine. Inline expansion or IPA would be necessary for
optimization to be performed safely.
Unoptimizable input or output statements found.
This loop was not optimized because it contains unoptimizable input or
output statements.