Open fermuch opened 5 years ago
Looks like it's a missing OPCode, i'll dig through the .wat and then see where its hanging.
This might be unrelated, but:
On opcodes.ex there is declared current_memory
and grow_memory
, but on instruction_parser.ex they are called memory_size
and memory_grow
@fermuch @fantypants That is exactly the issue. They should be called current_memory
and grow_memory
in both locations, respectively.
I was 98% certain we had one or the other, i think along our PR's its noted somewhere, I believe we changed it somewhere along the road.
Not too worry, I'll get it patched up right away
Trying the language poetry, I found WaspVM doesn't currently parse
current_memory
, which is not mentioned at the specification but seems to be valid on firefox, chrome and nodejs. Related issue on the spec: https://github.com/WebAssembly/design/issues/904Minimal poetry code which uses current_memory
WAT file
Traceback of the error