Accelerator Manual (G06.27+, H06.04+, J06.03+)
Error, Warning, and Note Messages
Accelerator Manual—527303-003
9-4
Note Messages
3. The Accelerator interprets a data region to be a code path.
Effect. The accelerated program executes correctly. The program makes a transition
into TNS code for the portion of code in which the Accelerator is uncertain about the
value of RP.
Recovery. Check other notes about return value sizes, and any warnings that the
value of the register pointer (RP) might have been misunderstood. Removing the
cause of those notes and warnings might remove this one as well.
For TAL programs in which this note appears within or near a CASE statement,
recompile the program with the version of TAL released after 15JUN91 and accelerate
the program again.
6
Cause. The Accelerator found a control transfer whose destination cannot be predicted
statically. The Accelerator issues this note for TAL programs that use CODE(SETP)
statements, for FORTRAN programs that use assigned GOTO statements, for
FORTRAN programs that contain functions with multiple entry or return points, and
COBOL programs that use ALTER statements.
Effect. The accelerated program executes correctly. If the destination of the jump is a
register-exact point, the program continues to execute in accelerated code. If the
destination of the jump is not a register-exact point, then the program makes a
transition into executing TNS code.
Recovery. For FORTRAN and COBOL programs, you must recode the program to
remove the constructs.
For TAL programs with CODE(SETP) statements, make sure that possible
CODE(SETP) targets are denoted by user-defined labels in the source code and that
the Accelerator input file contains symbols. While these steps will not eliminate this
note, they will ensure that execution stays in accelerated code.
7
Cause. The Accelerator found a SETE instruction that might modify the value of the
register pointer, RP.
Effect. The accelerated program executes correctly. If a SETE instruction modifies the
value of the register pointer, the program makes a transition into executing TNS code
from that point until the next procedure call.
Recovery. None needed.
Note 6: SETP instructions appear in the following procedure(s):
'<proc name>' at offset(s): <address>
Note 7: SETE instructions appear in the following procedure(s):
'<proc name>' at offset(s): <address>