Wenyong Huang

The issue should have been resolved in PR https://github.com/bytecodealliance/wasm-micro-runtime/pull/3209, after changing the the field `memory_data_size` of `WASMMemoryInstance` from type `uint32` to `uint64`, and removing the related code to resize the...

@erxiaozhou thanks for reporting the issue, it is similar to #3386 when handling the if block in loader: ```wast if (param i64 i64) (result i64 i64) ;; label = @1...

Close the issue since it was fixed.

Hi, it seems both two methods are not so straightforward, how about we just introduce a new API to set the native stack size required for the host native APIs?...

Yes, it is very similar to the first approach, but no need to make changes for current runtime native libraries implementation and developer's native library registration if there is no...

BTW, the api had better use module name as the first argument, like wasm_runtime_register_natives: `wasm_runtime_set_native_api_stacks(const char *module_name, NativeSymbolStack *native_stacks, uint32 n_symbol_stack)`

> Yes, it is very similar to the first approach, but no need to make changes for current runtime native libraries implementation and developer's native library registration if there is...

> > Yes, it is very similar to the first approach, but no need to make changes for current runtime native libraries implementation and developer's native library registration if there...

Yes, it is unused after some code refactorings and can be removed now.

Close this issue since the unused function was removed in https://github.com/bytecodealliance/wasm-micro-runtime/pull/3489.