The current TestRegs code only checks a few general purpose registers and then only for reading. The test should be checking as many registers as possible for reading, and ditto for writing.
Note that TestRegs was deleted, there's now TestRegisters (which came from TestRegMemModify). But the test should only worry about registers, TestMemory is checking the memory path.
now my bug
frysk.testbed.TestRegs added and instances in frysk.proc.live.TestRegs, frysk.stack.TestRegs added.