Inspect Manual

Using Inspect With Accelerated Programs on TNS/R
Systems
Inspect Manual—429164-006
16-2
Assumptions
correspondence between the state of the accelerated program and the state it would
have if executed on a TNS system—do not exist at all program locations. When not at
a synchronization point, memory and TNS registers may be “out of date.”
Both the hardware features of the system and the optimizations performed by OCA
may result in some debugging and execution differences when compared with
execution on a TNS system. Differences in program execution are referred to as
variances. The primary debugging difference for accelerated programs is that at some
points, the program may not have the same state that it would on a TNS system.
Figure 16-1 illustrates acceleration by Axcel, the accelerator for TNS/R systems. The
end product of acceleration by Axcel is a program file containing both TNS object code
and accelerated (RISC) object code.
Assumptions
If you use the Axcel accelerator to accelerate your program, you should have an
understanding of the accelerator. This not only includes the operation and syntax of the
accelerator, but also a conceptual understanding of its function. See the Accelerator
Manual for additional information.
To debug accelerated programs at the machine level, you should understand the
limitations and the TNS/R system variances. For more information, see Debugging
Programs at the TNS/R Machine Level on page 15-10 and the Accelerator Manual for
additional information.
Variances
Some infrequently used programming constructs do not work on TNS/R systems when
a program has been accelerated. Variances are differences between TNS and TNS/R
systems which can affect program execution. An example of a variance is the wrapping
of user data stack addresses. For more information about variances on TNS/R
systems, see the Accelerator Manual.
Figure 16-1. Acceleration of TNS Code on TNS/R Systems
TNS
Compiler
TNS
Object Code
Axcel
TNS
Object Code
vst1801.vsd
Accelerated
Object Code
(RISC)