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

Error, Warning, and Note Messages

Accelerator Manual—527303-003

9-8

Note Messages

Cause. The Accelerator cannot statically determine the return address because of

address map conflicts. The following code constructs can generate register-exact point

conflicts:

1. A procedure call immediately followed by a user-defined label or dynamic control

transfer (a SETP instruction)

2. A procedure call immediately followed by a secondary entry point to the current

procedure or subprocedure

3. A secondary entry point marked by a user-defined label

Effect. The accelerated program executes correctly. The program makes a transition

into TNS code at the procedure return, the dynamic control transfer, or the call to the

labelled entry point.

Recovery. None needed.

Cause. The named procedure was compiled without symbols, or the input file had

been stripped. The named procedure contains SETP instructions whose targets are

probably not register-exact points since the Accelerator did not have access to user

label information from the symbols region.

Effect. The SETP instruction probably caused a program to make a transition into

executing TNS code. It is highly probable that the Accelerator was not able to generate

accelerated code for large regions of code (any region that can only be reached

through that SETP instruction). All of the region on code that was not accelerated

executes as TNS code.

Recovery. Whenever possible, accelerate your code with a symbols region present.

Note 20: SETP instructions appear in the following

procedure(s) that have no symbols:

'<proc name>' at offset(s): <address>