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

The compiler and compiler directives you use determine the linker you must use and the kind of
executable object code that is produced:
Object CodeLinkerCompiler DirectiveCompiler
PICeldCALL_SHARED (default)EpTAL
NOCALL_SHARED (error)
PICldCALL_SHAREDpTAL
Non-PICnldNOCALL_SHARED (default)
The linker can also strip nonessential information from an object file and modify the object file’s
process attributes (such as HIGHPIN). For more information, see:
• eld Manual
• ld Manual
• nld Manual
The simplest cases are:
• On TNS/E, use the EpTAL compiler and the eld utility to create an object file that executes
on TNS/E (see Figure 14 (page 359)).
• On TNS/R, use the pTAL compiler and either the ld or nld utility to create an object file that
executes on TNS/R (see Figure 15 (page 360)).
Also, TNS allows you to create object files that execute on TNS/R. Use the TAL compiler and Binder
on TNS and the Accelerator (AXCEL) on either TNS or TNS/R to create an object file that executes
on TNS/R (see Figure 16 (page 361)). (In this case, you begin with TAL source code rather than
pTAL source code.)
You can input some kinds of loadfiles to the Accelerator (AXCEL) and the Object Code Accelerator
(OCA) to produce hybrid loadfiles (see Figure 17 (page 362)).
You cannot link PIC and non-PIC object files into a single object file.
Figure 14 Creating a Loadfile on TNS/E for TNS/E
Linking Object Files 359