TAL Programmer's Guide Data Alignment Addendum
Table Of Contents

TAL Programmer's Guide Data Alignment Addendum—524967-003
Glossary-1
Glossary
See also the glossary in the TAL Programmer’s Guide.
accelerated mode. See TNS accelerated mode.
aligned. In TNS/R native mode, a data item is aligned if its address is a multiple of its size; 
for example, a 4-byte data item is aligned if its byte address is a multiple of 4.
Explicitly Parallel Instruction Computing (EPIC). The technology that forms the basis for 
the Intel® Itanium® architecture. EPIC technology allows parallel processing 
opportunities to be explicitly identified by the compiler before the software code is 
executed by the processor.
misaligned. In TNS mode and accelerated mode, an erroneous address that is odd-byte 
aligned; in TNS/R native mode, an inefficient address that is not aligned.
native mode. See TNS/R native mode or TNS/E native mode.
release version update (RVU). A collection of compatible revisions of HP NonStop 
operating system software products, identified by an RVU ID, and shipped and 
supported as a unit. An RVU consists of the object modules, supporting files, and 
documentation for the product revisions. An RVU also includes a set of documentation 
for the overall RVU.
signal. The method by which an environment notifies a process of an event. Signals are 
used to notify a process when an error that is not related to input or output has 
occurred. Compare to trap.
TNS accelerated mode. A TNS emulation environment on a TNS/R or TNS/E system in 
which accelerated TNS object files are run. TNS instructions have been previously 
translated into optimized sequences of MIPS or Intel® Itanium® instructions. TNS 
accelerated mode runs much faster than TNS interpreted mode. Accelerated or 
interpreted TNS object code cannot be mixed with or called by native mode object 
code. Compare to TNS/R native mode and TNS/E native mode.
TNS interpreted mode. A TNS emulation environment on a TNS/R or TNS/E system in 
which individual TNS instructions in a TNS object file are directly executed by 
interpretation rather than permanently translated into MIPS or Intel® Itanium® 
instructions. TNS interpreted mode runs slower than TNS accelerated mode. Each 
TNS instruction is decoded each time it is executed, and no optimizations between 
TNS instructions are possible. TNS interpreted mode is used when a TNS object file 
has not been accelerated for that hardware system, and it is also sometimes used for 
brief periods within accelerated object files. Accelerated or interpreted TNS object code 
cannot be mixed with or called by native mode object code. Compare to TNS 
accelerated mode, TNS/R native mode, and TNS/E native mode.










