Replies: 2 comments 2 replies
-
Hi, did you build the iwasm from scratch, or just use the release iwasm binary? And the coremark wasm file isn't found, could you upload it? |
Beta Was this translation helpful? Give feedback.
1 reply
-
Hi, the default native stack size for child thread is a little small in the AOT mode, please enlarge it by manually changing the below line (e.g. change to wasm-micro-runtime/core/config.h Lines 434 to 435 in 217ba3b and build iwasm with lib-pthread support again: cd product-mini/platforms/linux
mkdir build && cd build
cmake .. -DWAMR_BUILD_LIB_PTHREAD=1
make -j Or define the macro in your CMakeLists.txt, e.g. add |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Subject of the issue
I have compiled Coremark-pro to wasm using wasi-sdk and running the .wasm file using wasm-micro-runtime(WAMR)
there are 9 workloads in coremark-pro in that parser-125k workload compiled to AOT, it is not running.
I am using the iwasm binary from wamr
I have compiled Coremark-pro to wasm using wasi-sdk and running the .wasm
Your environment
Steps to reproduce
when running the same for AOT
$ /coremark-pro_t1/builds/linux64/gcc64/bin$ ../../../../iwasm -v=5 - parser-125k.aot
###Tell us how to reproduce this error
Run the attached bin files one is .wasm and other is .aot with the iwasm
Expected behavior
for both wasm and AOT i shoud get the result or score as below
Actual behavior
In linker flags like below i am using values.
method1:-
If stack size is lesser than heap wasm module is working and generating score.
and with same values i ahve tried to run AOT module which is converted from wasm module.
with AOT module i am facing issue like Exception: native stack overflow
method2:-
Here i have increased stack size more than heap then wasm module itself is not generating score.
its giving error like
Beta Was this translation helpful? Give feedback.
All reactions