mirror of
https://github.com/bytecodealliance/wasm-micro-runtime.git
synced 2025-02-06 23:15:16 +00:00
4aee3cf14e
According to the specification: ``` When instantiating a module which is expected to run with `wasi-threads`, the WASI host must first allocate shared memories to satisfy the module's imports. ``` Currently, if a test from the spec is executed while having the `multi-module` feature enabled, WAMR fails with `WASM module load failed: unknown import`. That happens because spec tests use memory like this: `(memory (export "memory") (import "foo" "bar") 1 1 shared)` and WAMR tries to find a registered module named `foo`. At the moment, there is no specific module name that can be used to identify that the memory is imported because using WASI threads: https://github.com/WebAssembly/wasi-threads/issues/33, so this PR only avoids treating the submodule dependency not being found as a failure. |
||
|---|---|---|
| .. | ||
| iwasm_interp.cmake | ||
| SConscript | ||
| wasm_interp_classic.c | ||
| wasm_interp_fast.c | ||
| wasm_interp.h | ||
| wasm_loader.c | ||
| wasm_loader.h | ||
| wasm_mini_loader.c | ||
| wasm_opcode.h | ||
| wasm_runtime.c | ||
| wasm_runtime.h | ||
| wasm.h | ||