TAL Reference Summary

Warning Messages

110 096256 Tandem Computers Incorporated

6 Invalid ABSLIST addresses may have been generated

When the file reaches the 64K-word limit, the compiler disables ABSLIST, starts

printing offsets relative to the procedure base instead of to the code area base, and

emits this warning. Also, because the compiler is a one-pass compiler, some addresses

are incorrect when:

The file contains more than 32K words of code

RESIDENT procedures follow nonresident procedures

The PEP directive does not supply enough PEP table space

All procedures are not FORWARD (and no PEP directive appears)

If the file has more than 32K words of code space or if you use the stand-alone Binder,

do not use ABSLIST.

7 Multiply defined SECTION

name

The same section name appears more than once in the same SOURCE directive. The

compiler ignores all occurrences but the first. If omitting the code denoted by

duplicate section names adversely affects the program, replace the duplicate section

names with unique section names.

8 SECTION name not found

A section name listed on a SOURCE directive is not in the specified file. If omitting

such code adversely affects the program, specify the correct file name.

9 RP or S register mismatch

An operation contains conflicting instructions for the RP (register pointer) or the S

IF alpha THEN STACK 1 ELSE STACK 1D;

An example of S conflict is the following statement. The setting of the S register

depends on the value of ALPHA, which the compiler cannot determine at compile

time.

IF alpha THEN CODE (ADDS 1) ELSE CODE (ADDS 2);

The compiler might detect an RP or S conflict in source code that compiled without

problem in releases before C00. If the object code does not execute as intended, recode

the source code to eliminate the warning. You might only need to insert an RP or

DECS directive.