pTAL Reference Manual (G06.24+, H06.09+, J06.03+)

Table 6 EpTAL, pTAL, and TAL Compiler Characteristics
Object Code GeneratedCompiler
TNS/E object code—PIC (position-independent code)EpTAL
TNS/R object code—Non-PIC (default) or PICpTAL
TNS object code—Non-PICTAL
Difference between pTAL and EpTAL compilers:
EpTAL CompilerpTAL Compiler
On Guardian platforms, object files have the file code 800On Guardian platforms, object files have the file code 700
EpTAL code can use 64-bit addressing functionality added
to TNS/E pTAL starting with SPR T0561H01^AAP. For
pTAL code cannot use 64-bit addressing functionality added
to TNS/E pTAL starting with SPR T0561H01^AAP. For
more information, see Appendix E, “64-bit Addressing
Functionality” (page 531).
more information, see Appendix E, “64-bit Addressing
Functionality” (page 531).
The compilers in Table 6 execute under control of the HP NonStop operating systems in Table 7.
Table 7 HP NonStop Operating Systems
RVUArchitecture
TNS/E G06.20 and later
H06.01 and later
D40 and laterTNS/R
TNS C-series
D-series
This manual indicates when pTAL behaves differently on TNS/E and TNS/R architectures. When
no architecture is specifically mentioned, the syntax works the same way on TNS/E and TNS/R
architectures.
For more information:
SourceTopic
Intel Itanium Architecture Software Developer’s ManualItanium® chips used in TNS/E systems
MIPS RISC Architecture by Gerry Kane and Joe HeinrichRISC chips used in TNS/R systems
System description manual for your systemTNS/R or TNS/E architecture
Chapter 16 (page 355)Compiling pTAL source programs
pTAL Applications
The pTAL language is appropriate for writing applications where optimal performance has high
priority, for example:
• Systems software
Operating system components◦
◦ Compilers and interpreters
◦ Command interpreters
pTAL Applications 31