Details
- Reviewers
ldionne - Group Reviewers
Restricted Project - Commits
- rG30f9b47907e7: [libc++][CI] Test std module in C++26 mode.
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
libcxx/utils/ci/buildkite-pipeline.yml | ||
---|---|---|
214 | I am kinda worried about the explosion of the number of jobs. Is there a reason why we want to keep testing the std module in C++23? For example, we don't do that for Clang modules. We only test the latest standard version with Clang modules. |
libcxx/utils/ci/buildkite-pipeline.yml | ||
---|---|---|
214 | Yes and No. C++26 adds new named declarations not available in C++23. For example there are already 3 new headers accepted for C++26; hazard_pointer, rcu and text_encoding. So we need to test C++26 and C++23 separately. Based on our discussion regarding testing modules yesterday we may want to take a different approach for testing modules. |
libcxx/utils/ci/buildkite-pipeline.yml | ||
---|---|---|
214 | I know have a different approach where I reuse the existing job to build the module tests. So instead of adding a new job it adds a few tests to the existing job. This also solves the scalability for testing with different libc++ configurations. |
libcxx/utils/ci/buildkite-pipeline.yml | ||
---|---|---|
119–123 |