nld and noft Manual

nld Diagnostic Messages
nld and noft Manual—520384-003
10-47
Fatal Errors
**** ERROR **** [1209]:
The input object file named 'filename' appears to be
corrupted because there is a bad value in word number number
of the auxiliary symbol table. This word was expected to be
a pointer to the 'stEnd' entry in the local symbol table for
the procedure named name.
**** ERROR **** [1210]:
The parameters given for doing the cache optimization with
downward layout did not give enough space for the 'name'
section. Layout started at address-1 and needed to go down
as far as address-2, but the section starts at address-3.
**** ERROR **** [1211]:
There appears to be an inconsistency in NLD's input. NLD has
not created a 'farjump gateway' for the procedure named
name-1, but there is a call to this procedure from the
procedure named name-2 that would require a 'farjump
gateway'. This happens in the input object file named
'filename'.
**** ERROR **** [1212]:
The object file named 'filename' contains a form of code
generation that NLD cannot handle. There is a J or JAL
instruction at virtual address address-1 that has a target
address of address-2 within the same object file. This
target address has already been inserted into the
instruction, rather than using the relocation table to
describe the target address by pointing at a name listed in
the 'external symbol table'. Also, this target address is
not an address listed in the 'procedure descriptor table',
nor is it a location within the same procedure. NLD cannot
relocate this type of code.
**** ERROR **** [1213]:
The object file named 'filename' appears to be corrupted
because there is a relocation table entry with relocation
type 'R_MIPS_HI16' that is not immediately followed by an
entry with relocation type 'R_MIPS_LO16' referring to the
same symbol. This occurs at entry number number-1 within the
relocation table entries for the procedure named name.