-
Notifications
You must be signed in to change notification settings - Fork 256
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
wast: does not support recently added atypical condition test #1213
Comments
ia0
added a commit
to google/wasefire
that referenced
this issue
Sep 23, 2023
Kept the following a bit behind: - `third_party/WebAssembly/spec` because of bytecodealliance/wasm-tools#1213 - `generic-array` because RustCrypto don't use the 1.0.0 yet
alexcrichton
added a commit
to alexcrichton/wasm-tools
that referenced
this issue
Sep 25, 2023
Much of this code dates back to when this crate was trying to parse all of WABT's tests as well as the upstream test suite. WABT at the time had syntactical forms that weren't technically supposed to be valid given the upstream test suite, so at the time more was accepted than should be. This commit fixes how `(if ...)` is parsed to require `(then ..)` and `(else ..)` wrappers. Previously these were mistakenly only optional. Additionally this fixes bytecodealliance#1213 by allowing multiple condition-related folded expressions before `(then ..)`. This updates a few of the golden outputs for the spec test suites, notably those that use `(if (foo) (then) (else))` where previously `wast` would erroneously not emit an `else` instruction but now it does. Closes bytecodealliance#1213
Thanks for the report! This should be fixed in #1215 |
alexcrichton
added a commit
that referenced
this issue
Sep 25, 2023
* Clean up parsing `(if ...)` Much of this code dates back to when this crate was trying to parse all of WABT's tests as well as the upstream test suite. WABT at the time had syntactical forms that weren't technically supposed to be valid given the upstream test suite, so at the time more was accepted than should be. This commit fixes how `(if ...)` is parsed to require `(then ..)` and `(else ..)` wrappers. Previously these were mistakenly only optional. Additionally this fixes #1213 by allowing multiple condition-related folded expressions before `(then ..)`. This updates a few of the golden outputs for the spec test suites, notably those that use `(if (foo) (then) (else))` where previously `wast` would erroneously not emit an `else` instruction but now it does. Closes #1213 * Fix some test syntax
kofls
pushed a commit
to kofls/wasefire
that referenced
this issue
Nov 27, 2023
Kept the following a bit behind: - `third_party/WebAssembly/spec` because of bytecodealliance/wasm-tools#1213 - `generic-array` because RustCrypto don't use the 1.0.0 yet
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Parsing the
if.wast
file of the WebAssembly/spec test suite fails after WebAssembly/spec#1682.https://github.com/WebAssembly/spec/blob/bfb21e96f99820e0cfb0c41a264bd0d42795bfe2/test/core/if.wast#L530-L534
The text was updated successfully, but these errors were encountered: