From d31406b394307e5629372271f797f55c7ca9bbd3 Mon Sep 17 00:00:00 2001 From: David Spickett Date: Wed, 21 Feb 2024 10:20:02 +0000 Subject: [PATCH] [flang][docs] Update llvm-test-suite docs (#81596) With some missing config options and a link to the test suite docs that explain how to setup `ISO_FORTRAN_C_HEADER` and set the stop message variable. --- flang/docs/FortranLLVMTestSuite.md | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/flang/docs/FortranLLVMTestSuite.md b/flang/docs/FortranLLVMTestSuite.md index 45485ef40106..611e03cbad0e 100644 --- a/flang/docs/FortranLLVMTestSuite.md +++ b/flang/docs/FortranLLVMTestSuite.md @@ -21,7 +21,9 @@ cmake -G "Ninja" -DCMAKE_C_COMPILER= \ -DCMAKE_Fortran_COMPILER= \ -DTEST_SUITE_COLLECT_CODE_SIZE:STRING=OFF \ -DTEST_SUITE_SUBDIRS:STRING="Fortran" \ - -DTEST_SUITE_FORTRAN:STRING=ON .. + -DTEST_SUITE_FORTRAN:STRING=ON \ + -DTEST_SUITE_LIT= \ + ``` This will configure the test-suite to run only the Fortran tests which @@ -29,10 +31,15 @@ are found in the Fortran subdirectory. To run the C/C++ tests alongside the Fortran tests omit the `-DTEST_SUITE_SUBDIRS` CMake variable. -If your Fortran compiler is Flang, you may want to set the `NO_STOP_MESSAGE` -environment variable to `1` in order to avoid test failures due to warnings -about INEXACT signaling exceptions. +If your Fortran compiler is Flang, there are a couple of other things you need +to do, which are explained +[here](https://github.com/llvm/llvm-test-suite/blob/main/Fortran/gfortran/README.md#usage). +Then to build and run the tests: +``` +ninja +ninja check +``` ## Running the SPEC CPU 2017