Existing Jit>>do: method act as a bridge between software VM implementation and the JIT.
It works well, yet once compiled, block code remains in the JIT module. Currently JIT VM does not support recompilation of an arbitrary method because a lot of run-time references need to be cleared/updated.
In case of a console method we know that compiled version of it may be thrown away right after execution. We use this fact to allow easy management of interactive JIT blocks.
Jit>>once: should be added. It should work much the same except that compiled method and it's platform code are disposed after execution.
Existing
Jit>>do:method act as a bridge between software VM implementation and the JIT.It works well, yet once compiled, block code remains in the JIT module. Currently JIT VM does not support recompilation of an arbitrary method because a lot of run-time references need to be cleared/updated.
In case of a console method we know that compiled version of it may be thrown away right after execution. We use this fact to allow easy management of interactive JIT blocks.
Jit>>once:should be added. It should work much the same except that compiled method and it's platform code are disposed after execution.