Wenyong Huang

The issue should have been resolved with #3209, see also #2468, #2530.

Windows uses libc-uvwasi by default, the result may be different.

@matsbror I guess the ceilf/floor symbol not found issue is related to: https://github.com/bytecodealliance/wasm-micro-runtime/blob/main/core/iwasm/compilation/aot_emit_numberic.c#L1052-L1065 And you can dump the LLVM IR generated to see more details: ```bash wamrc --format=llvmir-unopt -o test.ll...

Got it, we didn't test llvm jit on RISCV64 yet. Maybe you can dump llvm module by enabling the code here: https://github.com/bytecodealliance/wasm-micro-runtime/blob/main/core/iwasm/compilation/aot_compiler.c#L2662-L2665

> it's trivial to make the loads volatile. i wonder how much performance penalty it would involve for real applications, which is typically already optimized when compiled into wasm. It...

> In my opinion, any instructions related to memory, global variables, table and element sections, etc. that involve the state of the runtime execution process shouldn't be optimized as much...

> I think it's an acceptable result if it really impacts the performance since dead code appears rarely in real world cases. A `warning` for elimination of dead `load/store` instructions...

> > > is this basically a copy from wamr-app-framework? > > > > > > Yes, I should have mentioned it in the PR description. > > please update...

> > > > > is this basically a copy from wamr-app-framework? > > > > > > > > > > > > Yes, I should have mentioned it...

> Actually I was thinking, what if we only save the pointer here > > https://github.com/bytecodealliance/wasm-micro-runtime/blob/c0e33f08b04a5e03220ef74c2a9dbea8f1f35996/core/iwasm/common/wasm_c_api.c#L2286-L2292 > > instead of copying? That would allow more control and fix the problem...