[all-commits] [llvm/llvm-project] eebe9b: [libc++][modules] Adds module testing.

[Mark de Wever via All-commits]

  Branch: refs/heads/users/mordante/adds_module_testing
  Home:   https://github.com/llvm/llvm-project
  Commit: eebe9b2fab5c5eef4776852270bf70af4626cfcb
      https://github.com/llvm/llvm-project/commit/eebe9b2fab5c5eef4776852270bf70af4626cfcb
  Author: Mark de Wever <koraq at xs4all.nl>
  Date:   2024-01-12 (Fri, 12 Jan 2024)

  Changed paths:
    M libcxx/docs/TestingLibcxx.rst
    M libcxx/modules/std/memory.inc
    M libcxx/test/libcxx/module_std.gen.py
    M libcxx/test/libcxx/module_std_compat.gen.py
    A libcxx/test/libcxx/selftest/modules/no-modules.sh.cpp
    A libcxx/test/libcxx/selftest/modules/std-and-std.compat-module.sh.cpp
    A libcxx/test/libcxx/selftest/modules/std-module.sh.cpp
    A libcxx/test/libcxx/selftest/modules/std.compat-module.sh.cpp
    M libcxx/test/std/modules/std.compat.pass.cpp
    M libcxx/test/std/modules/std.pass.cpp
    M libcxx/utils/libcxx/test/features.py
    M libcxx/utils/libcxx/test/format.py
    M libcxx/utils/libcxx/test/modules.py

  Log Message:
  -----------
  [libc++][modules] Adds module testing.

This adds a new module test infrastructure. This requires tagging tests
using modules. The test runner uses this information to determine the
compiler flags needed to build and use the module.

Currently modules are build per test, which allows testing them for
tests with ADDITIONAL_COMPILE_FLAGS. At the moment only 4 tests use
modules. Therefore the performance penalty is not measurable. If in the
future more tests use modules it would be good to measure the overhead
and determine whether it's acceptable.