Wenyong Huang

Close this PR as another PR is under review instead: #3823.

> do you mean to have a single global shared memory, which all wasm modules with a linear memory on the system can fully access? i guess it would be...

> Awesome. At the W3C in person event, Deepti presented on providing a `mmap` function. In her use case this is used to `mmap` hardware memory into the WASM VM's...

@no1wudi yes, maybe we can add another option for wamrc to allow to call runtime API to do boundary check in AOT/JIT mode, but I am not sure whether it...

> > Yes, in current discussion, it is supposed to only have a global shared heap, each wasm module can access it, and the shared heap is created during runtime...

> Would it be possible to have a module default to using `shared_malloc` / `shared_free` when making `malloc` / `free` calls without rewriting the code? > > Example use case:...

Hi, a possible way that I can think is to find which object file implements the `emscripten_builtin_malloc` in emsdk's libc.a and then remove it from libc.a, for example, `emar libc.a...

@iKlask 32bit may take longer time to run fib with the same argument, and it may take very long time to run fib with large input argument, had you tested...

Hi, maybe you can dump some logs to check whether the AOT file gets stuck, here is the wast file I refactored based on you wasm file, and note that...

How do you create the iwasm.sln and related make files for x86 on windows? I use `cmake .. -DWAMR_BUILD_TARGET=X86_32`, but the project configuration of generated iwasm.sln is set to x64...