Wasm testsuite malformations #14
Merged
Conversation
This file contains 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
ensure reserved bytes are zero ensure leb128 do not overflow ensure max locals is 2^32-1 decode data count and use it to verify data segments size catch multiple start functions require data count when memory instructions are present ensure sections are consumed ensure sections match size declared catch case where custom section is malformed ensure name values are correctly encoded utf8 catch leb128 cases of poor encoding
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
ensure reserved bytes are zero
ensure leb128 do not overflow
ensure max locals is 2^32-1
decode data count and use it to verify data segments size
catch multiple start functions
require data count when memory instructions are present
ensure sections are consumed
ensure sections match size declared
catch case where custom section is malformed
ensure name values are correctly encoded utf8
catch leb128 cases of poor encoding