-
Notifications
You must be signed in to change notification settings - Fork 787
wasm-opt missing support for table.fill #5939
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
Comments
You're the first person to ever ask for table.fill support! I can add it today. |
Merged
tlively
added a commit
that referenced
this issue
Sep 16, 2023
This instruction was standardized as part of the bulk memory proposal, but we never implemented it until now. Leave similar instructions like table.copy as future work. Fixes #5939.
tlively
added a commit
that referenced
this issue
Sep 18, 2023
This instruction was standardized as part of the bulk memory proposal, but we never implemented it until now. Leave similar instructions like table.copy as future work. Fixes #5939.
Any chance |
There's no active work at the moment, but we might implement |
radekdoulik
pushed a commit
to dotnet/binaryen
that referenced
this issue
Jul 12, 2024
This instruction was standardized as part of the bulk memory proposal, but we never implemented it until now. Leave similar instructions like table.copy as future work. Fixes WebAssembly#5939.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While wasm-opt appears to support
table.grow
correctly, any compiled module containing atable.fill
instruction will fail to parse. This is true even if you pass the appropriate--enable-reference-types
flag.Sample code:
change the
#if 0
to#if 1
and the resulting built module will cause wasm-opt to fail with something like:From checking the spec,
17
istable.fill
. Looking through the repo it seems like support fortable.init
andtable.copy
might be missing too, but I'm not planning to use them...The text was updated successfully, but these errors were encountered: