Test that 0xff is treated as an invalid opcode.#1910
Merged
rossberg merged 1 commit intoWebAssembly:wasm-3.0from May 20, 2025
Merged
Test that 0xff is treated as an invalid opcode.#1910rossberg merged 1 commit intoWebAssembly:wasm-3.0from
rossberg merged 1 commit intoWebAssembly:wasm-3.0from
Conversation
Following up on WebAssembly#1900, this tests that 0xff is disallowed as an instruction and instruction prefix byte.
rossberg
approved these changes
May 20, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Following up on #1900, this tests that 0xff is disallowed as an instruction and instruction prefix byte.