You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the llvm compiler along with the native engine, and bulk_memory instructions like memory.copy seem to cause panics.
Additional details
It looks like certain wasm bulk memory operators, such as MemoryCopy, are not implemented by compiler-llvm. In cases when certain instructions are run (memory.copy, memory.fill, etc), the wasm execution will crash, hitting this default case.
My wasmer dependency in Cargo.toml looks like this:
wasmer = { version = "1.0.2", default-features = false, features = ["wat", "default-native", "default-llvm" ] }
The text was updated successfully, but these errors were encountered:
We support TableCopy, TableInit and ElemDrop because those are used by the reference types proposal (as well as TableFill and TableGrow which aren't in the bulk memory proposal) but not the other operators.
Thanks for the clarification @nlewycky! Is there any plan to add those extra couple memory ops? It looks like bulk_memory is a finished proposal at this point and is making its way into browsers, so it'd be really nice for compatibility.
Summary
I'm using the llvm compiler along with the native engine, and bulk_memory instructions like
memory.copy
seem to cause panics.Additional details
It looks like certain wasm bulk memory operators, such as
MemoryCopy
, are not implemented bycompiler-llvm
. In cases when certain instructions are run (memory.copy
,memory.fill
, etc), the wasm execution will crash, hitting this default case.My
wasmer
dependency inCargo.toml
looks like this:The text was updated successfully, but these errors were encountered: