Update pinned llvm-compat nightly to 2024-01-01 / LLVM 17 #5647
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
Manishearth
force-pushed
the
llvmnightlyup
branch
2 times, most recently
from
a10d396
to
524c1d1
Compare
Manishearth
force-pushed
the
llvmnightlyup
branch
5 times, most recently
from
50a0b63
to
70252c7
Compare
|
This doesn't work because of dtolnay/proc-macro2#451 |
Manishearth
force-pushed
the
llvmnightlyup
branch
from
70252c7
to
6caa88f
Compare
|
I'd still like to try and upgrade the LLVM version |
Manishearth
force-pushed
the
llvmnightlyup
branch
from
6caa88f
to
23bcbcb
Compare
Manishearth
changed the title
|
This won't fix CI, but it passes, and it seems good to stay on latest commonly available LLVM. LLVM 17 seems to be everywhere, 18 is still a bit hard to get. |
sffc
approved these changes
Oct 3, 2024
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.
Fixes CI issues because test-c-tiny uses an old rustc that isn't able to understand the lockfile updated by test-c (rust-lang/cargo#14595).
We should also consider having the lockfiles cleaned between jobs.