Handle reentrant host calls #60
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes an issue I found where a host function calling back into WASM would cause the stack to get into an unrecoverable state.
Detect nested calls via operand stack, save/restore instruction pointer, and preserve results.
Detect nested CreateInvoker calls by checking the operand stack height. Save the current instruction pointer for nested calls and restore it on success or exceptions instead of unconditionally flushing the call stack. For nested calls push results back onto the operand stack so callers can consume them; for top-level calls keep the previous behavior of clearing remaining stack values.