Update riscv64 image to clang17 #96827
Conversation
ghost
added
the
community-contribution
|
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsCurrent version: clang15 Since risc-v is relatively a new architecture and toolchains are still in the process of implementing new extensions and optimizations overall, we should prefer the latest version for CI build validations.
|
am11
added
area-Infrastructure
arch-riscv
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsCurrent version: clang15 Since risc-v is relatively a new architecture and toolchains are still in the process of implementing new extensions and optimizations overall, we should prefer the latest version for CI build validations.
|
|
riscv64 picked up clang 17. -- The C compiler identification is Clang 17.0.6
-- The CXX compiler identification is Clang 17.0.6
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/clang-17 - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/clang++-17 - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
Detected Linux riscv64 |
|
Sounds good, but we don't need to merge the PR since the floating tag will get updated. |
|
ah, I thought the production ones take longer: https://github.com/dotnet/versions/commits/main/build-info/docker/image-info.dotnet-dotnet-buildtools-prereqs-docker-production.json, but apparently staging also push the floating tags (so what's the difference 🤷). It was picked up in main via floating tag. So Closing. :) |
|
Yeah looks like the -production.json is no longer used, it wasn't updated for almost a year. I've asked for clarification in dotnet/dotnet-buildtools-prereqs-docker#956 |
Current version: clang15
New version: clang17
Since risc-v is relatively a new architecture and toolchains are still in the process of implementing new extensions and optimizations overall, we should prefer the latest version for CI build validations.