-
Notifications
You must be signed in to change notification settings - Fork 654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use the WAMR_BUILD_PERF_PROFILING under llvm-jit #2372
Comments
@hungryzzz Thanks for reporting the issue! I submitted PR #2384 to fix it, could you please try again? |
wenyongh
added a commit
that referenced
this issue
Jul 24, 2023
LVM JIT failed to lookup symbol "aot_stack_sizes" as it is an internal symbol, change to lookup "aot_stack_sizes_alias" instead. Reported in #2372.
@wenyongh I've tried it and it works well. Thanks! |
victoryang00
pushed a commit
to victoryang00/wamr-aot-gc-checkpoint-restore
that referenced
this issue
May 27, 2024
…lliance#2384) LVM JIT failed to lookup symbol "aot_stack_sizes" as it is an internal symbol, change to lookup "aot_stack_sizes_alias" instead. Reported in bytecodealliance#2372.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I build
WAMR
using the configuration.cmake .. -DWAMR_BUILD_FAST_JIT=1 -DWAMR_BUILD_JIT=1 -DWAMR_BUILD_MEMORY_PROFILING=1 -DWAMR_BUILD_PERF_PROFILING=1
But when I try to use it under
--llvm-jit
option, there will an error raised as followed.WASM module instantiate failed: set instance running mode failed.
So how can I get the profiling data under llvm-jit?
Thank you!
The text was updated successfully, but these errors were encountered: