Marcin Kolny

> However, a user has requested to implement these requirements on Windows, which also needs to support os_mmap(). Could you clarify why is Windows the problem? There's already an existing...

Thanks, I think this value indeed can overflow, but I'm not sure there's much we can do about it - we could potentially saturate the value, but given how the...

@kripken based on my tests the pass is executed before passes for removing dead code, but I wasn't sure if that's just coincident or a stable behavior. Could you confirm...

Thanks for sharing. This sort of solves the problem I'm trying to solve; one difference here is that for `wasm-metadce` you need to define reachable nodes, whereas this pass does...

Not sure if that helps, but native function has access to the exec_env structure, so in order to obtain the call stack, you could do something like (haven't tested, so...

Yes, similarly, the function index can be calculated by doing the following: ```cpp auto* inst = wasm_runtime_get_module_inst(env); (uint32)(frame->function - inst->e->functions); ``` see implementation of the `wasm_interp_create_call_stack` function https://github.com/bytecodealliance/wasm-micro-runtime/blob/886f9444b9633f9af1bd3268ddbe7877a05de0f2/core/iwasm/interpreter/wasm_runtime.c#L4040 for more...

Hi @bcm0, thanks a lot for your interest. Could you please provide a bit more details about how do you compile/attempt to run the application and what are the errors?...

yeah I agree this seems like incorrect behavior. @lucasAbadFr would you like to provide a fix for it? If not, I might have some time next week to address the...

Are there any users relying on the multi-module support today that can not easily port to dynamic linking (i.e. recompile their code while upgrading WAMR)? Given that mult-module is very...

> Maybe we can allocate a buffer in the libc heap of host managed heap for the side module. Not sure what do you mean by the `host managed heap`?...