Update mariner images to latest with LLVM 16 #84676
Merged
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
ghost
assigned 
dotnet-issue-labeler
bot
added
the
needs-area-label
This was referenced Apr 12, 2023
jeffhandley
added
area-Infrastructure-coreclr
and removed
needs-area-label
|
Tagging subscribers to this area: @hoyosjs Issue DetailsSame as #84148, with extra changes to pull in dotnet/dotnet-buildtools-prereqs-docker#840.
|
sbomer
changed the title
jkoritzinsky
approved these changes
May 6, 2023
|
I ran PlaintextPlatform aspnet benchmarks with these changes and didn't see a performance diff one way or another. Thanks @sebastienros! FYI @richlander |
|
Build failures are #85949 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 pulls in the updates from dotnet/dotnet-buildtools-prereqs-docker#864 and moves to floating tags for the mariner images, which now build the product with LLVM 16.
Once this flows to dotnet-optimization, this will require updates to make the LLVM 16 tools available there. Before the opt data collected with new LLVM flows into runtime, I plan to fix #85785 so that local builds won't by default require clang-16.