-
Notifications
You must be signed in to change notification settings - Fork 693
llvm versions we use doesn't build with the latest Xcode #4210
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
Labels
Comments
possible fixes: |
I prefer bump llvm. |
yamt
added a commit
to yamt/wasm-micro-runtime
that referenced
this issue
Apr 25, 2025
yamt
added a commit
to yamt/wasm-micro-runtime
that referenced
this issue
Apr 27, 2025
yamt
added a commit
to yamt/wasm-micro-runtime
that referenced
this issue
May 1, 2025
yamt
added a commit
to yamt/wasm-micro-runtime
that referenced
this issue
May 6, 2025
yamt
added a commit
to yamt/wasm-micro-runtime
that referenced
this issue
May 6, 2025
cf. bytecodealliance#4210 why 19, not 20? because, as of writing this, 19 is the latest released version for the xtensa fork of llvm: https://github.com/espressif/llvm-project while we can use different versions for different targets, it's nicer to use the same version everywhere when possible.
yamt
added a commit
to yamt/wasm-micro-runtime
that referenced
this issue
May 7, 2025
cf. bytecodealliance#4210 why 19, not 20? because, as of writing this, 19 is the latest released version for the xtensa fork of llvm: https://github.com/espressif/llvm-project while we can use different versions for different targets, it's nicer to use the same version everywhere when possible.
yamt
added a commit
to yamt/wasm-micro-runtime
that referenced
this issue
May 8, 2025
cf. bytecodealliance#4210 why not 20? because, as of writing this, 19 is the latest released version for the xtensa fork of llvm: https://github.com/espressif/llvm-project why not 19? because of a bug in the xtensa fork of llvm: espressif/llvm-project#112 while we can use different versions for different targets, it's nicer to use the same version everywhere when possible.
lum1n0us
pushed a commit
that referenced
this issue
May 9, 2025
* build-scripts/build_llvm.py: bump to llvm 18 cf. #4210 why not 20? because, as of writing this, 19 is the latest released version for the xtensa fork of llvm: https://github.com/espressif/llvm-project why not 19? because of a bug in the xtensa fork of llvm: espressif/llvm-project#112 while we can use different versions for different targets, it's nicer to use the same version everywhere when possible. * spec-test-script/runtest.py: --size-level=0 for x86-64 with the recent version of LLVM, wamrc --size-level=1 often generates R_X86_64_32S relocations which fail on load with the infamous error: "relocation truncated to fit R_X86_64_32S failed" it seems that these relocations are often for jump tables. this commit workarounds it with --size-level=0. an alternative is to disable jump tables. (although it seems that jump tables are not the only source of these relocations.) cf. #3035 it might be better to do this in wamrc itself. however, currently target info is not available there in case of native compilation. related: #3356 * wamr-compiler: size_level=0 for sgx mode cf. #3035
sjamesr
pushed a commit
to sjamesr/wasm-micro-runtime
that referenced
this issue
May 13, 2025
* build-scripts/build_llvm.py: bump to llvm 18 cf. bytecodealliance#4210 why not 20? because, as of writing this, 19 is the latest released version for the xtensa fork of llvm: https://github.com/espressif/llvm-project why not 19? because of a bug in the xtensa fork of llvm: espressif/llvm-project#112 while we can use different versions for different targets, it's nicer to use the same version everywhere when possible. * spec-test-script/runtest.py: --size-level=0 for x86-64 with the recent version of LLVM, wamrc --size-level=1 often generates R_X86_64_32S relocations which fail on load with the infamous error: "relocation truncated to fit R_X86_64_32S failed" it seems that these relocations are often for jump tables. this commit workarounds it with --size-level=0. an alternative is to disable jump tables. (although it seems that jump tables are not the only source of these relocations.) cf. bytecodealliance#3035 it might be better to do this in wamrc itself. however, currently target info is not available there in case of native compilation. related: bytecodealliance#3356 * wamr-compiler: size_level=0 for sgx mode cf. bytecodealliance#3035
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
llvm (lldb) versions used by wamr doen't build with latest Xcode
because Xcode dropped std:char_traits:
https://developer.apple.com/documentation/xcode-release-notes/xcode-16_3-release-notes
(search "The base template for std::char_traits has been removed" in the page)
llvm 18 and later has this fixed:
llvm/llvm-project@68744ff
llvm/llvm-project@7549cde
cd wamr-compiler ./build_llvm_xtensa.sh --project clang lldb
The text was updated successfully, but these errors were encountered: