Working towards better handling of stack balance with break and continue exceptions.
Stop crashing in interactive testing. (The unknown and history mechanisms tend
to exercise some parts of the bytecode compiler very well.)
update comments
Added the tests I want to pass...
Do jump generation at places where INST_RETURN_IMM might occur.
Tackle evalStk by reusing existing machinery.
Improve coverage of [error] compilation.
Added missing exception range finalize.
Fix handling of 'invokeExpanded' and start to do 'returnStk'.
And the last bits that need fixing; the code is still less efficient than desired but should now not crash.
[2835313] Ensure correct stack balance when break and continue exceptions are about: the hard cases with potential concealed exception generation.