[clang][CI] Reuse build dir between C++26 and modules build of runtimes #132480
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.
Between C++26 and Clang modules build of runtimes, which are used as an additional testing for Clang, the only difference are
LIBCXX_TEST_PARAMS
andLIBCXXABI_TEST_PARAMS
. Both of them are transformed into actual lit configuration lines, and put intoSERIALIZED_LIT_PARAMS
, which end up inlibcxx/test/cmake-bridge.cfg
viaconfigure_file
command. Notably, it seems that they are not used in any other way.I checked that if those variables are changed, subsequent runs of CMake configuration step regenerate
cmake-bridge.cfg
with the new values. Which means that we don't need to do clean builds for every runtimes configuration we want to test.I hope that together with #131913, this will be enough to alleviate Linux CI pains we're having, and we wouldn't have to make a tough choice between C++26 and Clang modules builds for pre-merge CI.