H06.03 ReadMe

to the ME on the X fabric, then open the CLCI and CNSL
windows on the Y fabric.
4.0 APPLICATIONS and COMPILERS FOR H06.03
4.1 Compilers Not Available
-----------------------------
Cross-compilers are not available to build code on an Integrity
NonStop NS-series Server for use on a TNS/R platform.
4.2 TNS for OSS
------------------
The TNS compilers and utilities are available only for the Guardian
environment. They are not available for the OSS environment. Code that
runs in the OSS environment must be converted to use the native
compilers to run on H-series. For more information, see the H06.03
Release Version Update Compendium and the H-Series Application
Migration Guide.
4.3 TNS/E Compiler Debugging
------------------------------
Reporting incorrect address range:
The compiler emits address ranges for which the value of a
variable is available. In certain cases, when two statements are
consecutive to each other, but are separated by nops, the ranges can
be off by one or two instructions (nops). The user might not
completely be within the range. In this situation, the value
displayed for the variable might reflect the old value before the
modification. This only happens with optimization level 1 (-01) code.
To prevent this problem from occurring, compile the affected routine
at optimization level 0.
Reporting incorrect line number:
The debugger indicates, for example, that it is at line X after
a step, even though the program can't possibly be at that line. This
might give the impression that the statement has executed when it
actually has not. The program itself is correct, but the
debugger is reporting an incorrect line number because the
instruction where execution has stopped was not given a correct line
number by the compiler.
To recover, perform the step again to get to a valid statement
beginning.
To prevent this incorrect line number from occurring, compile the
affected routine at optimization level 0.
Page
8
of
12