BRK opcode

Coordinator
Feb 11, 2011 at 4:18 AM

Currently, BRK opcode switches the system into the out-of-process ML monitor.  Not sure if we will keep it that way.  The true BRK opcode performs some actions that dont work well in the current context.  Normally, it jumps to a high vector after pushing things to the stack.  Without a kernal, there's nowhere to jump to, and would BRK forever.  Perhaps it should instantiate the OOP monitor if the resulting location contains a BRK also.