[all-commits] [llvm/llvm-project] 8f863f: [clang][CI] Reuse build dir between C++26 and modu...

[Vlad Serebrennikov via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 8f863fcd77e15caf3b7fde089adc223b0c4fb103
      https://github.com/llvm/llvm-project/commit/8f863fcd77e15caf3b7fde089adc223b0c4fb103
  Author: Vlad Serebrennikov <serebrennikov.vladislav at gmail.com>
  Date:   2025-03-25 (Tue, 25 Mar 2025)

  Changed paths:
    M .ci/monolithic-linux.sh

  Log Message:
  -----------
  [clang][CI] Reuse build dir between C++26 and modules build of runtimes (#132480)

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` and `LIBCXXABI_TEST_PARAMS`. Both of them are
transformed into actual lit configuration lines, and put into
`SERIALIZED_LIT_PARAMS`, which end up in `libcxx/test/cmake-bridge.cfg`
via `configure_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.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications