-
Notifications
You must be signed in to change notification settings - Fork 452
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
invalid type mismatch #290
Milestone
Comments
I think this is related too, the following test fails to return the correct value
|
so when I arrange all the params to be at the top then the locals everything works |
Thanks. I introduced this bug when I removed the original index space
distinction between parameters and locals. They do not get reordered
properly. I will look into a fix.
|
Addressed in #291 by making a misplaced |
rossberg
added a commit
that referenced
this issue
May 30, 2016
Fixes #290 by imposing a strict order on param, result, and local declarations.
ngzhian
pushed a commit
to ngzhian/spec
that referenced
this issue
Nov 4, 2021
ngzhian
added a commit
to ngzhian/spec
that referenced
this issue
Nov 4, 2021
This is a simple change, validation and execution is already shape-agnostic, so we only need to add it to the syntax. Instructions were merged in WebAssembly#290.
ngzhian
added a commit
to ngzhian/spec
that referenced
this issue
Nov 4, 2021
This was merged in WebAssembly#290. Also tweaked the file generation scripts: - Make simd_arithmetic more generic (allow different instruction name patterns) - create a new file simd_int_to_int_widen to generate all integer widening operations (including the ones implemented in this PR) - remove widening tests from simd_conversions.wast
rossberg
added a commit
that referenced
this issue
Feb 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following code generates this error when ran
test.wast:21.28-21.42: type mismatch: expression has type i32 but the context requires i64
code:
if I remove one (and it doesn't matter which one)
param
orlocal
it runs without errorThe text was updated successfully, but these errors were encountered: