Change History (9)
comment:1 by , 10 years ago
comment:3 by , 10 years ago
The reason for the clock tests is that the original hardware clock was unreliable; an argument could be made for surrounding the tests in "If (cpu is not dps8m_emulator)."
The RSW instuction provides bits identifiying the CPU and optional features, and a number of bits are reserved for future expansion, and are guarenteed to be zero. One of the reserved bits could be assigned "dps8m emulator" or "clock is stable" semantics, and be leveraged by scas_init. -- Charles
comment:4 by , 10 years ago
| Milestone: | → MR12.6a |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
comment:5 by , 10 years ago
| Version: | → MR12.5 |
|---|
comment:6 by , 10 years ago
In the version in MR12.6a, Multics could still crash under the emulator in two cases. This component was updated in MR12.6b to work better with the emulator.
comment:7 by , 10 years ago
| Milestone: | MR12.6a → MR12.6b |
|---|
comment:9 by , 9 years ago
| Summary: | Fix scas_init to be more tolerant of processor speed. → Fix scas_init to be more tolerant of processor speed (MCR10001) |
|---|

Ticket moved here from https://sourceforge.net/p/dps8m/tickets/60/