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

Using the Accelerator
Accelerator Manual—527303-003
4-9
Specifying the Debugging Mode
user code. Note that user library code not identified as such to the Accelerator cannot
be used as a user library or a shared run-time library at execution time.
Accelerating User Libraries and Shared Run-Time Libraries
To accelerate a user library or a shared run-time library, accelerate the TNS object file
as user library code by specifying the UL option. In the following example, the TNS
user library MyLib is accelerated and written to the MyLibAx file:
AXCEL MyLib, MyLibAx; UL
Accelerate your library file before you accelerate any user code programs that call it. If
you change the interface to any non-extensible routines in a library, both the library and
the user code programs that call it must reaccelerate. If you only change the routine
internals, only the library must reaccelerate. When you accelerate a user code
program, specify a UserLib option for the accelerated library file called by the user
code program. Refer to Specifying Accelerated Libraries on page 4-10 for details.
Accelerating System Processes
To accelerate a system process, accelerate the TNS object file as user code. You
might get Warning 37 from the Accelerator (“UC option in effect, but input file has no
main procedure.”). This warning can be safely ignored because system processes do
not require a main procedure.
Never accelerate any code supplied by HP.
Accelerating Your Own SC and SL Procedures
If you add procedures to system code or system library, you must accelerate them
before running the SYSGEN process:
•
To accelerate a module that you want to add into system code, specify the SC
option.
•
To accelerate a module that you want to add into system library, specify the SL
option.
The SC and SL options set the Linkable option. The Linkable option generates code
that can be bound into system code or system library by the XLLINK tool. NotLinkable
is the default if UC or UL is set. Refer to the SYSGEN Reference Manual for more
information about adding procedures to system code and system library.
Specifying the Debugging Mode
To make debugging easier, you can control how the Accelerator optimizes procedures.
By default, the Accelerator optimizes across an entire procedure at one time, making
changes to the code to improve its performance without changing its results. For
debugging purposes, however, this default option has the side effect of blurring the
relationship between source language statements.