Wenyong Huang

Yes, please try: ```diff diff --git a/core/iwasm/aot/aot_loader.c b/core/iwasm/aot/aot_loader.c index 759954ad..3e832c27 100644 --- a/core/iwasm/aot/aot_loader.c +++ b/core/iwasm/aot/aot_loader.c @@ -2917,6 +2917,17 @@ do_text_relocation(AOTModule *module, AOTRelocationGroup *group, } symbol_addr = module->func_ptrs[func_index]; } + else...

Please see #3231.

Hi, it doesn't have to be at least 64KB, please refer to [How to reduce the footprint](https://github.com/bytecodealliance/wasm-micro-runtime/blob/main/doc/build_wasm_app.md#2-how-to-reduce-the-footprint), and: https://github.com/bytecodealliance/wasm-micro-runtime/blob/main/doc/memory_tune.md https://github.com/bytecodealliance/wasm-micro-runtime/blob/main/doc/memory_usage.md

> Thank you. > > **EDIT:** **I realize now no need to compile wamrc for 32 bit in my case. the fixes in aot_loader are intended for the 32bit runtime....

@tonibofarull I am not sure whether it is a bug, could you help look into it? Thanks a lot.

@mkolchurin it is really hard to support these ancient zephyr versions, I believe that they are rarely used by zephyr developers now, maybe we just don't add the version control...

Hi, yes, the multi-memory is an important feature and is planned, but due to the resource limitation, we will try to implement it after the memory64 feature is enabled (see...

Hi, thanks for spotting the issue, the aot debugger wasn't tested on windows yet, could you try the below patch: ```diff diff --git a/core/iwasm/aot/debug/elf_parser.c b/core/iwasm/aot/debug/elf_parser.c index 657f9530..7b0c57b8 100644 --- a/core/iwasm/aot/debug/elf_parser.c...

https://github.com/bytecodealliance/wasm-micro-runtime/pull/3370

Hi, this is a defect currently, since the type of field memory_data_size in WASMMemoryInstance is uint32, its max value is UINT32_MAX and we don't want to change the AOT ABI...