Accelerator Manual (G06.27+, H06.04+, J06.03+)

Error, Warning, and Note Messages
Accelerator Manual—527303-003
9-7
Note Messages
Effect. The Accelerator probably had to guess the return value sizes based on the
context at the subprocedure call sites. Note 15 shows the sizes that the Accelerator
guessed. The accelerated program executes correctly since a run-time check verifies
the guess. If the guess is correct, then the program continues to execute accelerated
code upon return from the subprocedure call. If the guess is incorrect, the program
makes a transition into executing TNS code upon return from the subprocedure call.
Recovery. None. You cannot use the ReturnValSize option for subprocedures.
15
Cause. The Accelerator performs static analysis on subprocedures to determine their
return value sizes. The Accelerator predicted the value of the register pointer, RP, at
the subprocedure exit point (because of a dynamic procedure call, for example), so the
Accelerator was unable to determine the correct return value size.
Effect. The accelerated program executes correctly since a run-time check verifies the
guess. If the guess is correct, then the program continues to execute accelerated code
upon return from the subprocedure call. If the guess is incorrect, the program makes a
transition into executing TNS code upon return from the subprocedure call.
Recovery. None. You cannot use the ReturnValSize option for subprocedures.
Resolving other notes might eliminate this one.
17
Cause. The named procedure contains a SETL instruction that might change the
return address on the execution stack.
Effect. The accelerated program executes correctly. If the SETL instruction changes
the return address, and that address is not a register-exact point, then your program
makes a transition into executing TNS code when the procedure returns.
Recovery. If the program does change the return address, make sure that it returns to
a register-exact point. While this recovery action does not make Note 17 disappear, it
ensures that the program executes in accelerated code.
19
Note 15: The Accelerator could not determine the return value
size of the following subprocedures:
Subprocs embedded in procedure '<proc name>':
Entry at offset <address>;
Guessed return size <value>, <n> times
Note 17: SETL instructions appear in the following
procedure(s): '<proc name>' at offset(s): <address>
Note 19: The following locations have register-exact point
conflicts so no register-exact points are emitted:
'<proc name>' at offset(s): <address>