Need Help | wat2wasm: "error: unexpected token" about wabt

[sbc100]

What kind of response did you expect from running the get export? Presumably wasmtime is running get but are you expecting it to print the result somehow? Perhaps its returning the result as the return code?

Perhaps ask in the wasmtime support forums?

[keithw]

If you want to run the tests in that file, you can use wabt's interpreter (with the spectest imports):

$ ./bin/wast2json ./third_party/testsuite/left-to-right.wast -o /tmp/ltr/left-to-right.json
$ ./bin/spectest-interp /tmp/ltr/left-to-right.json
96/96 tests passed.

To run an individual exported function (without the spectest imports available):

$ ./bin/wasm-interp /tmp/ltr/left-to-right.0.wasm --run-export=i32_call_indirect
i32_call_indirect() => i32:66052

[sbc100]

left-to-right.wast is not a wat file (a single module) but a wast file, which can contains many modules and also assertions about the module. This is the format used by the spec test.

If you want to process wast files, such as those found in the spec test, wabt does have a tool called wast2json which is used to split a wast into a set of wat files, along with a json description of the assertions.

[shamb0]

Thanks @sbc100,

With help of your suggestion, I've successfully extracted the wasm file from wast using the wast2json tool by following these steps:

./out/clang/Debug/wast2json \
    --enable-all \
    ./third_party/testsuite/left-to-right.wast \
    -o ../temp01-shamb0-test/left-to-right.json

• The resulting files are:

.
├── left-to-right.0.wasm
└── left-to-right.json

• I attempted to test the wasm file with wasmtime using this command:

RUST_LOG=trace ./target/debug/wasmtime \
    --debug debug-info=true \
    ../temp01-shamb0-test/left-to-right.0.wasm \
    --invoke get 2

• However, I did not receive a response from wasmtime. Could you advise on how to effectively test the extracted wasm file?

Your guidance is appreciated.

[shamb0]

Thank you @keithw, following your suggestion, I successfully ran the wasm file using wasm-interp.

Thanks to @sbc100's pointer, I will check with the 'wasmtime' team regarding the observed behavior.