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.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
MCR10001 addressed this issue.
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.
Closed as ticket moved to http://multics-trac.swenson.org/ticket/34