[all-commits] [llvm/llvm-project] 382b70: [libc++] Add coverage for C++17 and Clang Modules ...
Louis Dionne via All-commits
all-commits at lists.llvm.org
Thu Mar 20 10:51:21 PDT 2025
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: 382b707e52ee6a0ca9a799795362dee67ade993f
https://github.com/llvm/llvm-project/commit/382b707e52ee6a0ca9a799795362dee67ade993f
Author: Louis Dionne <ldionne.2 at gmail.com>
Date: 2025-03-20 (Thu, 20 Mar 2025)
Changed paths:
M .github/workflows/libcxx-build-and-test.yaml
A libcxx/cmake/caches/Generic-modules-cxx17-lsv.cmake
R libcxx/cmake/caches/Generic-modules-lsv.cmake
M libcxx/test/libcxx/atomics/atomics.syn/incompatible_with_stdatomic.verify.cpp
M libcxx/utils/ci/run-buildbot
M libcxx/utils/libcxx/test/params.py
Log Message:
-----------
[libc++] Add coverage for C++17 and Clang Modules with LSV (#131815)
In recent versions of Clang, using -std=c++20 (and later) implies LSV
when compiling with modules. This change resulted in making our LSV job
redundant with the regular modules job, which uses the latest Standard.
This patch increases the coverage of our CI without increasing its cost
by pinning the LSV job to use C++17, which normally doesn't use LSV. A
related question is whether we should add coverage for non-LSV builds
using Clang modules.
To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications
More information about the All-commits
mailing list