Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix parsing of select-with-results #872

Merged
merged 1 commit into from
Jan 5, 2023

Conversation

alexcrichton
Copy link
Member

Previously multiple (result) blocks would erroneously discard the previously parsed result blocks, so this commit fixes the textual parsing of this instruction to collect all of the (result) blocks instead of only the final one.

Closes #870

Previously multiple `(result)` blocks would erroneously discard the
previously parsed result blocks, so this commit fixes the textual
parsing of this instruction to collect all of the `(result)` blocks
instead of only the final one.

Closes bytecodealliance#870
@alexcrichton alexcrichton marked this pull request as ready for review January 5, 2023 16:48
@alexcrichton alexcrichton merged commit d79620f into bytecodealliance:main Jan 5, 2023
@alexcrichton alexcrichton deleted the fix-select-parse branch January 5, 2023 18:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

wasm-parser: should typed select parse with result arity ≠ 1?
2 participants