-
Notifications
You must be signed in to change notification settings - Fork 9
LLVM 20 transition #3594
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
Comments
Noted some warnings when building 20.1.2,
we'd better to fix it in #3600 as well. |
Building compiler-rt as a project instead of runtime seems to mess the buildsystem up, leading to visibility of symbols in compiler-rt are incorrectly set to default. This is the root cause #3839. The change is temporarily reverted1. We should finish the transition first. |
Our builders have upgraded to LLVM 20, so we must workaround this when reworking
|
LLVM doesn't support -fno-plt on RISC-V and LoongArch and starts emitting a warning if it's supplied on unsupported targets since LLVM 20, causing various errors when configuring packages. Let's remove the flag on riscv64 and loongarch64. As we have started moving to LLVM 20, the problem must be mitigated by stripping -fno-plt away from CFLAGS/LDFLAGS on riscv64 and loongarch64. Link: llvm/llvm-project#124081 Reference: eweOS#3594 (comment)
LLVM doesn't support -fno-plt on RISC-V and LoongArch and starts emitting a warning if it's supplied on unsupported targets since LLVM 20, causing various errors when configuring packages. Let's remove the flag on riscv64 and loongarch64. As we have started moving to LLVM 20, the problem must be mitigated by stripping -fno-plt away from CFLAGS/LDFLAGS on riscv64 and loongarch64. Link: llvm/llvm-project#124081 Reference: #3594 (comment)
Clang 20 starts to error on void functions whose parameters are applied with This affects libtg_owt: issue desktop-app/tg_owt#150, workaround PR #3991 Reference: llvm/llvm-project#113460 |
Uh oh!
There was an error while loading. Please reload this page.
TODO
-fno-plt
on riscv64 and loongarch64, where LLVM doesn't support the option and emits a warning starting from LLVM 20Is it necessary to wait for Rust 1.87.0? (will stablize on May 15th)2025.05.11: The transition has been completed!
Workarounds/Bugs to recheck after upgrading
[ ] vala: ICE on riscv64caused by stability problems of one of our builder.The text was updated successfully, but these errors were encountered: