Skip to content

Commit d31406b

Browse files
[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.
1 parent 3533fe7 commit d31406b

File tree

1 file changed

+11
-4
lines changed

1 file changed

+11
-4
lines changed

flang/docs/FortranLLVMTestSuite.md

+11-4
Original file line numberDiff line numberDiff line change
@@ -21,18 +21,25 @@ cmake -G "Ninja" -DCMAKE_C_COMPILER=<path to C compiler> \
2121
-DCMAKE_Fortran_COMPILER=<path to Fortran compiler> \
2222
-DTEST_SUITE_COLLECT_CODE_SIZE:STRING=OFF \
2323
-DTEST_SUITE_SUBDIRS:STRING="Fortran" \
24-
-DTEST_SUITE_FORTRAN:STRING=ON ..
24+
-DTEST_SUITE_FORTRAN:STRING=ON \
25+
-DTEST_SUITE_LIT=<path to llvm-lit> \
26+
<path to llvm-test-suite>
2527
```
2628

2729
This will configure the test-suite to run only the Fortran tests which
2830
are found in the Fortran subdirectory. To run the C/C++ tests
2931
alongside the Fortran tests omit the `-DTEST_SUITE_SUBDIRS` CMake
3032
variable.
3133

32-
If your Fortran compiler is Flang, you may want to set the `NO_STOP_MESSAGE`
33-
environment variable to `1` in order to avoid test failures due to warnings
34-
about INEXACT signaling exceptions.
34+
If your Fortran compiler is Flang, there are a couple of other things you need
35+
to do, which are explained
36+
[here](https://github.com/llvm/llvm-test-suite/blob/main/Fortran/gfortran/README.md#usage).
3537

38+
Then to build and run the tests:
39+
```
40+
ninja
41+
ninja check
42+
```
3643

3744
## Running the SPEC CPU 2017
3845

0 commit comments

Comments
 (0)