Add LLVM 18 builds #704
Merged
Add LLVM 18 builds #704
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
nathanchance
requested review from
nickdesaulniers,
JustinStitt and
bwendling
as code owners
llvm_latest is now 18. Move the current llvm_latest builds to llvm_17, so that no coverage is lost. Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
bwendling
approved these changes
Jan 31, 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.
This moves LLVM latest from 17 to 18 by adding separate LLVM 17 builds based on LLVM latest and moving the LLVM latest anchor to
18and copying all of the LLVM tip of tree builds over, gaining more build coverage.I am not sure if TuxSuite has been updated to allow specifying
clang-18yet. That is a switch in the backend though, so it should be easy to correct if it has not been done already.