wasm-micro-runtime/core/iwasm
Wenyong Huang ef3a683392
Don't call start/initialize in child thread's instantiation (#1967)
The start/initialize functions of wasi module are to do some initialization work
during instantiation, which should be only called one time in the instantiation
of main instance. For example, they may initialize the data in linear memory,
if the data is changed later by the main instance, and re-initialized again by
the child instance, unexpected behaviors may occur.

And clear a shadow warning in classic interpreter.
2023-02-17 15:11:05 +08:00
..
aot Don't call start/initialize in child thread's instantiation (#1967) 2023-02-17 15:11:05 +08:00
common Modify poll_oneoff in libc-wasi to make it interruptible (#1951) 2023-02-16 21:03:33 +08:00
compilation Make memory profiling show native stack usage (#1917) 2023-02-01 11:52:15 +08:00
fast-jit Enable running mode control for runtime and module instance (#1923) 2023-02-02 18:16:01 +08:00
include Improve wasm-c-api instantiation-time linking (#1902) 2023-02-13 15:06:04 +08:00
interpreter Don't call start/initialize in child thread's instantiation (#1967) 2023-02-17 15:11:05 +08:00
libraries Modify poll_oneoff in libc-wasi to make it interruptible (#1951) 2023-02-16 21:03:33 +08:00
README.md Enable AoT and wamr-sdk, and change arguments of call wasm API (#157) 2020-01-21 13:26:14 +08:00