-
Notifications
You must be signed in to change notification settings - Fork 21
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
Something broken in JS test case generation #95
Comments
The wast itself seems fine; it's clear that there is no difference except the i64 index, and indeed it should return |
This looks like a bug in the JS conversion backend. WebAssembly/spec#1836 should fix it, PTAL. |
This in particular includes WebAssembly/memory64#96 which fixes WebAssembly/memory64#95 via WebAssembly/spec#1836. [email protected] Bug: 364917766, 364913810 Change-Id: I62ad43742628216f4b0385b4f837212a57b76108 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5973202 Reviewed-by: Eva Herencsárová <[email protected]> Commit-Queue: Clemens Backes <[email protected]> Cr-Commit-Position: refs/heads/main@{#96887}
I am trying to get the newest spec tests to pass in V8. I am stuck at a problem which seems to be on the spec side.
Take this example (reduced from
table_fill.wast
):I run this through
test/core/run.py --out /tmp test.wast
.The resulting
test.js
contains:This looks like a reasonable straight-forward translation.
The second assertion translates to:
The
run
function exported by the module is this:This obviously results in
unreachable
being executed.Does anyone spot what is broken here?
@bvisness @sbc100 @rossberg
Note: If the
br
would be abr_on_non_null
, the test would test what it's supposed to test. No idea though if generating this was the intention.The text was updated successfully, but these errors were encountered: