-
Notifications
You must be signed in to change notification settings - Fork 4
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
Adding tests #2
Comments
@rossberg, do we have precedent for how we would even test the extended name section? |
@tlively in the annotations proposal the reference interpreter is extended to handle arbitrary custom sections (and annotations). here is the handler for the name section: https://github.com/WebAssembly/annotations/blob/main/interpreter/custom/handler_name.ml and corresponding tests: https://github.com/WebAssembly/annotations/blob/main/test/custom/name/name_annot.wast a custom handler can do any validation it wishes, and in the tests one can write a regular The tests for The ones for branch hinting are here: https://github.com/WebAssembly/branch-hinting/blob/main/test/custom/metadata.code.branch_hint/branch_hint.wast What is needed is a way to represent the section in the text format. This can be either a corresponding annotation, or the generic If we are going to remove the |
What @yuri91 said, i.e., not until now, but there is infrastructure for validating and round-tripping custom sections in the annotations repo. So perhaps it's easiest to rebase on that proposal. However, that repo is a bit outdated, and I'm currently in the process of syncing it with upstream (which is a bit painful since we switched parsers upstream). Will let you know here when I'm done. |
Okay, that was really painful, but this repo is now up to date with upstream. |
Thank you, both! |
Since initial support was added to binaryen (#1) I decided to add preliminary support to wabt : WebAssembly/wabt#1554
I wonder if its time to add some tests here and try to move this proposal forward to the next stage?
The text was updated successfully, but these errors were encountered: