Trailing-Edge
-
PDP-10 Archives
-
bb-bt99e-bb
-
lnkv51.d09
There is 1 other file named lnkv51.d09 in the archive. Click here to see a list.
EDIT DESCRIPTIONS FOR LINK-10-V5-1
EDIT 2067 FOR LINK
[SYMPTOM]
Entering a filename such as NUL:FOO will cause an illegal instruction
trap.
[DIAGNOSIS]
Edit 2014 causes the stack to be off by 6 when NUL: is used.
[CURE]
Handle NUL: correctly by not doing an ADJSP if the device was NUL:.
********************************************************************************
EDIT 2070 FOR LINK
[SYMPTOM]
LINK may suppress loading of a program if the left half of .JBERR is
nonzero.
[DIAGNOSIS]
LINK checks the entire word, .JBERR, to determine if there were any
compilation errors. If .JBERR is nonzero then loading is suppressed.
This is incorrect; only the right half of .JBERR is reserved for the
error count.
[CURE]
Check only the right half of .JBERR to determine if there were any
compilation errors.
********************************************************************************
EDIT 2071 FOR LINK
[SYMPTOM]
LINK sources contain definitions which are already in various system
.UNV files. This is unnecessary and is not good programming practice.
Duplicate definitions include some JSYSes, .GTxxx bits, and PDV words.
[DIAGNOSIS]
The definitions were needed in LINK because they were first used
before the .UNV files had them. This is no longer necessary.
[CURE]
Remove the duplicate definitions.
********************************************************************************
EDIT 2072 FOR LINK
[SYMPTOM]
The 102x block processor has two problems. The start address and
subsequent relocation bytes are not picked up properly and there is a
typo which causes data to be stored in the wrong halfword.
[DIAGNOSIS]
The first relocation byte is not being stepped over before picking up
the start byte. The typo for the halfword store needs to be fixed.
[CURE]
Skip the first relocation byte and fix the typo.
********************************************************************************
EDIT 2073 FOR LINK
[SYMPTOM]
Undeserved LNKPEL, LNKPTL, LNKHCL, LNKOLC, and other messages when
loading programs with more than 18 overlays, if some are writable.
[DIAGNOSIS]
LINK uses the address of the global symbol containing the base of
the writable overlay table, instead of its contents. This causes
LINK to store into accumulator zero instead of into the table,
trashing the flags which are normally in accumulator zero.
[CURE]
Use the contents of the location, rather than its address.
********************************************************************************
EDIT 2074 FOR LINK
[SYMPTOM]
Incorrect symbol table, LNKSFU errors, or other problems.
[DIAGNOSIS]
LINK attempts to determine whether or not it must expand the LC or
HC window by subtracting the lower address needed from the upper
address, and checking this against the size of the window.
However, this can be one page too small because the window is page
aligned, and the addresses needed are not.
[CURE]
Put the upper address at the top of the page.
********************************************************************************
EDIT 2075 FOR LINK
[SYMPTOM]
Building LINK-10 results in warnings that .SGNAM, .SGDEV, and .SGPPN
are obsolete.
[DIAGNOSIS]
LINK uses the old symbols to obtain information if the GETTAB fails.
[CURE]
Remove the old symbols from LINK and issue a fatal error instead of
trying the old offsets if a GETTAB fails.
********************************************************************************
END OF LINK-10-V5-1