pTAL Reference Manual (H06.08+)

Compiling and Linking pTAL Programs

HP pTAL Reference Manual—523746-006

16-7

Linking Object Files

The linker links one or more linkfiles to produce either a loadfile or another linkfile.

The compiler and compiler directives you use determine the linker you must use and

the kind of executable object code that is produced:

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 16-2 on page 16-8).

•

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 16-3 on page 16-9).

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-4 on page 16-10). (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 16-5 on page 16-11).

You cannot link PIC and non-PIC object files into a single object file.

Compiler Compiler Directive Linker Object Code

EpTAL CALL_SHARED (default) eld PIC

NOCALL_SHARED (error)

pTAL CALL_SHARED ld PIC

NOCALL_SHARED (default) nld Non-PIC