Wenyong Huang

[Refactor APIs and data structures as preliminary work for Memory64](https://github.com/bytecodealliance/wasm-micro-runtime/commit/0ee5ffce8573a0e41f5a33dce562f541e98eb28a) was merged into main.

https://github.com/bytecodealliance/wasm-micro-runtime/pull/3240 https://github.com/bytecodealliance/wasm-micro-runtime/pull/3260 https://github.com/bytecodealliance/wasm-micro-runtime/pull/3266

Hi, when hw bound check is enabled, aot_call_function calls invoke_native_with_hw_bound_check, in which the EXCE_NATIVE_STACK_OVERFLOW check is already added. When hw bound check isn't enabled, it calls invoke_native_internal instead, which doesn't...

@b4yuan thanks for submitting the PR! It is really a good method to improve WAMR's code quality. IIUC, we should address the issues reported below before merging this PR? https://github.com/bytecodealliance/wasm-micro-runtime/security/code-scanning?query=pr%3A2812+is%3Aopen

Merge this PR and will create another PR to enhance it: (1) add more compilation combinations to build many kinds of iwasm with different features enabled, (2) run the CI...

@b4yuan Thanks again for contributing this PR, it is really important to improve the code quality of WAMR project. I have merged this PR and submitted another PR (#3246) to...

@erxiaozhou thanks for spotting the issue, it was fixed with #3112, please pull the latest code to test again.

Close this issue since it had been resolved.

Hi, "wasi proc exit" is a normal behavior and the exception will be cleared by runtime before wasi app main function returns. https://github.com/bytecodealliance/wasm-micro-runtime/blob/8b37048823677d9229b7458b064a515b19744c9c/core/iwasm/common/wasm_application.c#L132-L137 Please use `wasm_runtime_get_exception` to check whether there...

Hi, yes, the "wasi proc exit" is only thrown when the wasm app is a wasi module, and it is cleared by runtime if the function to call is "_start"...