You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a nice exception system, and it could probably be extended to support this.
When an exception is thrown, the handlers are queued onto the call stack, followed by a termination instruction. If we don't queue the termination instruction, we could "handle" an exception and then resume code.
The main issue is preserving the general-purpose registers (and possibly some other register info) when we do this.
The text was updated successfully, but these errors were encountered:
We have a nice exception system, and it could probably be extended to support this.
When an exception is thrown, the handlers are queued onto the call stack, followed by a termination instruction. If we don't queue the termination instruction, we could "handle" an exception and then resume code.
The main issue is preserving the general-purpose registers (and possibly some other register info) when we do this.
The text was updated successfully, but these errors were encountered: