Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[libc++][CI] Upgrade compiler HEAD version to Clang-20 #108761

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

robincaloudis
Copy link
Contributor

@robincaloudis robincaloudis commented Sep 15, 2024

Why

The release branch for LLVM 19.x is created (release/19.x) as anounced here. As a result, the version on main is now 20.0.0git. Therefore, we no longer officially support Clang-17, but instead Clang-{18,19,20}.

What

Upgrade HEAD version to Clang-20 in CI configs. Adjustments for libc++ tests and implementations will be done in follow-up patches.

Copy link

github-actions bot commented Sep 15, 2024

✅ With the latest revision this PR passed the Python code formatter.

@robincaloudis robincaloudis force-pushed the rc-ci-clang-20 branch 2 times, most recently from 2fa7cdb to 7c9c19a Compare September 15, 2024 15:35
@robincaloudis robincaloudis changed the title [libc++][CI] Update to Clang-20 [libc++][CI] Upgrade HEAD version to Clang-20 Sep 15, 2024
philnik777 pushed a commit that referenced this pull request Sep 15, 2024
Before changing the compiler version in
#108761, we first of all need
to upgrade the HEAD version to `Clang-20` in the Docker files and push
new builder images to the CI.
@robincaloudis robincaloudis changed the title [libc++][CI] Upgrade HEAD version to Clang-20 [libc++][CI] Upgrade compiler HEAD version to Clang-20 Sep 15, 2024
@robincaloudis robincaloudis force-pushed the rc-ci-clang-20 branch 2 times, most recently from 3e9a7ab to ed34e6d Compare September 15, 2024 18:43
LLVM_OLDEST_VERSION: "17"
LLVM_HEAD_VERSION: "20" # Used compiler, update POST-BRANCH.
LLVM_PREVIOUS_VERSION: "19"
LLVM_OLDEST_VERSION: "18"
GCC_STABLE_VERSION: "13"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
GCC_STABLE_VERSION: "13"
GCC_STABLE_VERSION: "14"

Just an off-topic question: Shouldn't this value be 14?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for pointing out! This env variable might be unused. It seems to me that the actual version for gcc is configured here. I will double check my claim.

# if _LIBCPP_CLANG_VER < 1700
# warning "Libc++ only supports Clang 17 and later"
# if _LIBCPP_CLANG_VER < 1800
# warning "Libc++ only supports Clang 18 and later"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The buildkite builds fail because AIX, arm, FreeBSD use Clang 17 still:
https://buildkite.com/llvm-project/libcxx-ci/builds/37764#0192014a-8840-47ea-b2bf-31aa8dd679de/2158-2953

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great hint! Thanks. I did not yet finalized this PR (hence the draft) as we're still working on updating the CI images. This is not yet finished. As long as the images for the CI builders are not updated, this PR will not work. I keep you updated.

Let's adjust tests and implementation
in a seperate PR.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants