Wenyong Huang

> Hi @wenyongh. Yeah, I also wasn't sure the memory wrapper approach would be the best choice, so I'm not surprised to hear you don't love it either. I could...

Close this PR since #3845 and #3887 have been merged.

Hi, could you run the workload with AOT mode? You can [build the aot compiler (wamrc)](https://github.com/bytecodealliance/wasm-micro-runtime/blob/main/wamr-compiler/README.md) first, and then use it to compile the wasm file into aot file: `wamrc...

Hi, it is interested to support fibers. Currently the `exec_env->native_stack_boundary` is updated in each time `wasm_call_function/aot_call_function`, which calls `wasm_exec_env_set_thread_info` to get native stack boundary from os and update it. Per...

I uploaded PR #3862, could you check whether it resolves your issue? You can call wasm_runtime_set_native_stack_boundary to set the native stack boundary to exec_env.

Close this issue since https://github.com/bytecodealliance/wasm-micro-runtime/pull/3862 was merged.

Hi, there is no plan yet. Maybe you can try to support it by yourself, refer to [WAMR porting guide](https://github.com/bytecodealliance/wasm-micro-runtime/blob/main/doc/port_wamr.md) and the implementation of other platforms for more details.

@xianjimli Thanks for reporting the issue! I have several questions: which global mutex do you refer to, and do you mean the global mutex is accessed after it is destroyed?...

@sjamesr thanks for reporting the issue, one of WAMR's goals is to reduce the footprint and the runtime may shrink the linear memory based on the global `__data_end`, `__stack_top` and...

Hi, `try_merge_data_and_text` is called only when the aot module is not in indirect mode (`module->is_indirect_mode` is false): https://github.com/bytecodealliance/wasm-micro-runtime/blob/deacb7a8d8ca96b9dff797907b7e3b2ced4887df/core/iwasm/aot/aot_loader.c#L3757-L3758 But `module->is_indirect_mode` is set to true when the input is an XIP...