LLVM 20 #22780
Draft
LLVM 20 #22780
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexrp
added
work in progress
This needs to be cherry-picked to master when we want to start testing the llvm20 branch on the CI machines.
See: * https://discourse.llvm.org/t/rfc-freezing-c-03-headers-in-libc/77319 * https://discourse.llvm.org/t/rfc-project-hand-in-hand-llvm-libc-libc-code-sharing/77701 We're dropping support for C++03 for Zig due to the first change; it would be insane to ship 1018 duplicate header files just for this outdated use case. As a result of the second change, I had to bring in a subset of the headers from llvm-libc since libc++ now depends on these. Hopefully we can continue to get away with not copying the entirety of llvm-libc.
LLVM is increasingly making use of this module flag when present.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See: #22014
Currently targeting LLVM 20.1.0-rc2.
Lots of regressions this time around:
test-fmt: ✔️test-cases: ✔️test-translate-c: ✔️test-run-translated-c: ✔️test-behavior: https://gist.github.com/alexrp/32ce477b5181656b8d2e2e261ded4dc5test-c-import: ✔️test-compiler-rt: ✔️test-universal-libc: ✔️test-std: https://gist.github.com/alexrp/e8ff151d6d1b4a8975677190a4e209ectest-unit: ✔️test-compare-output: ✔️test-standalone: https://gist.github.com/alexrp/8c8a5515d0e2b77805264ad3d9ab69d5test-c-abi: ✔️test-link: https://gist.github.com/alexrp/f6b74cc29873a5e4faa9718f84d13234test-stack-traces: https://gist.github.com/alexrp/27228c4c931bb1831cf5b734789becbdtest-cli: ✔️test-asm-link: ✔️test-debugger: ❓test-incremental: ✔️Bugs filed upstream:
llvm::isUIntN(BitWidth, val) && "Value is not an N-bit unsigned value"when building musl formips64-linux-muslabi64with Clang 20.1.0-rc1 llvm/llvm-project#125954llvm::isUIntN(BitWidth, val) && "Value is not an N-bit unsigned value"when using@llvm.usub.with.overflowon Hexagon llvm/llvm-project#127296llvm::isUIntN(BitWidth, val) && "Value is not an N-bit unsigned value"forload volatilefrom hardcoded pointer onpowerpc-linux-musleabihfllvm/llvm-project#127298