Fortran tests now go in top-level Fortran subdirectory and can be run with or without C/C++ tests.
Fortran tests are still excluded by default.
Differential D103354
[test-suite] Decouple Fortran tests from C/C++ tests. naromero77 on May 28 2021, 11:12 PM. Authored by
Details Fortran tests now go in top-level Fortran subdirectory and can be run with or without C/C++ tests. Fortran tests are still excluded by default.
Diff Detail
Event TimelineComment Actions I suggest to put each test into its own directly, i.e. the hello test into Fortran/UnitTests/hello. This would allow selecting each test separately using TEST_SUITE_SUBDIRS (instead of having to select all Fortran UnitTests/Benchmarks at the same time) and each test can itself decide whether it is using llvm_singlesource() or llvm_multisource(). Comment Actions
Comment Actions Ideally, how a test is executed is entirely specified in one file (the CMakeLists.txt), instead split between two files. In the standard case, a lit.local.cfg should not be required. I don't expect a redesign of the build system, so LGTM.
|
With config.traditional_output, stderr, stdout and the error code are implicitly redirected to a .out file . If false, the stderr/stdout files are specified explicitly. I think it is meant as a compatibility switch to make rewriting the build to CMake easier.