1
0
mirror of https://github.com/wfjm/w11.git synced 2026-02-24 08:22:21 +00:00

docu updates [skip ci]

This commit is contained in:
wfjm
2022-12-21 12:58:05 +01:00
parent 78e033cda7
commit 0875d4e8fa
24 changed files with 133 additions and 85 deletions

View File

@@ -9,7 +9,6 @@ Beyond that, the 11/70 and the J11 logic are very different
- the 11/70 checks for writes with specifiers with mode 1, 2, 4, or 6, thus for
- `clr (sp)`
- `mov #77,(sp)+`
- `mov #77,(sp)+`
- `mov #77,-(sp)`
- `mov #77,2(sp)`
- the J11 checks for all accesses with specifiers with mode 4 and 5, thus for
@@ -21,9 +20,14 @@ The 11/70 logic focuses on that a write was done, while the J11 logic focuses
on that the `SP` was decremented.
SimH uses the J11 behavior for all models, thus also for an 11/70 simulation.
xxdp `ekbbf0` tests 36,40 and 42,
`ekbee1` tests 122 and 123,
`eqkce1` tests 41 and 65,
depend on the 11/70 behavior and are patched or skipped.
xxdp program `ekbbf0` tests 036, 040 and 042,
`ekbee1` tests 122 and 123, and
`eqkce1` tests 041 and 065
depend on the 11/70 behavior and are patched or skipped
(see patch for [ekbbf0](../tools/xxdp/ekbbf0_patch_1170.scmd),
[ekbee1](../tools/xxdp/ekbee1_patch_1170.scmd), and
[eqkce1](../tools/xxdp/eqkce1_patch_1170.scmd)).
The w11 correctly implements the 11/70 behavior.
The w11 correctly implements the 11/70 behavior. This is verified in a
[tcode](../tools/tcode/README.md), the test is skipped when executed on SimH
(see [cpu_details.mac](../tools/tcode/cpu_details.mac) test A3.3).