mirrors/llvm-project
0
0
Fork 0
mirror of https://github.com/llvm/llvm-project.git synced 2025-04-18 03:56:41 +00:00
Code Issues Projects Releases Wiki Activity

[flang][docs] Update llvm-test-suite docs (#81596)

Browse Source 
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.
This commit is contained in:
David Spickett 2024-02-21 10:20:02 +00:00 committed by GitHub
parent 3533fe783d
commit d31406b394
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 11 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
flang/docs/FortranLLVMTestSuite.md
View File

@ -21,7 +21,9 @@ cmake -G "Ninja" -DCMAKE_C_COMPILER=<path to C compiler> \
-DCMAKE_Fortran_COMPILER=<path to Fortran compiler> \ -DCMAKE_Fortran_COMPILER=<path to Fortran compiler> \
-DTEST_SUITE_COLLECT_CODE_SIZE:STRING=OFF \ -DTEST_SUITE_COLLECT_CODE_SIZE:STRING=OFF \
-DTEST_SUITE_SUBDIRS:STRING="Fortran" \ -DTEST_SUITE_SUBDIRS:STRING="Fortran" \
-DTEST_SUITE_FORTRAN:STRING=ON .. -DTEST_SUITE_FORTRAN:STRING=ON \
-DTEST_SUITE_LIT=<path to llvm-lit> \
<path to llvm-test-suite>
``` ```
This will configure the test-suite to run only the Fortran tests which 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 alongside the Fortran tests omit the `-DTEST_SUITE_SUBDIRS` CMake
variable. variable.
If your Fortran compiler is Flang, you may want to set the `NO_STOP_MESSAGE` If your Fortran compiler is Flang, there are a couple of other things you need
environment variable to `1` in order to avoid test failures due to warnings to do, which are explained
about INEXACT signaling exceptions. [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 ## Running the SPEC CPU 2017