Mercurial > hg > CbC > CbC_llvm

comparison flang/docs/FortranLLVMTestSuite.md @ 223:5f17cb93ff66 llvm-original

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
LLVM13 (2021/7/18)
author Shinji KONO <kono@ie.u-ryukyu.ac.jp>
date Sun, 18 Jul 2021 22:43:00 +0900
parents 79ff65ed7e25
children c4bab56944e8
comparison
equal deleted inserted replaced
222:81f6424ef0e3 223:5f17cb93ff66
19 19
20 ## Running the LLVM test-suite with Fortran 20 ## Running the LLVM test-suite with Fortran
21 21
22 Fortran support can be enabled by setting the following CMake variables: 22 Fortran support can be enabled by setting the following CMake variables:
23 ``` 23 ```
24 % cmake -DCMAKE_Fortran_COMPILER=<path to Fortran compiler> \ 24 cmake -G "Ninja" -DCMAKE_C_COMPILER=<path to C compiler> \
25 -DTEST_SUITE_FORTRAN:STRING=ON \ 25 -DCMAKE_CXX_COMPILER=<path to C++ compiler> \
26 -C../test-suite/cmake/caches/O3.cmake \ 26 -DCMAKE_Fortran_COMPILER=<path to Fortran compiler> \
27 ../test-suite 27 -DTEST_SUITE_COLLECT_CODE_SIZE:STRING=OFF \
28 -DTEST_SUITE_SUBDIRS:STRING="Fortran" \
29 -DTEST_SUITE_FORTRAN:STRING=ON ..
28 ``` 30 ```
29 31
30 At the moment, there is only a "hello world" Fortran test. A current 32 This will configure the test-suite to run only the Fortran tests which
31 shortcoming in the design of the test suite is that building the C/C++ 33 are found in the Fortran subdirectory. To run the C/C++ tests
32 tests is conflated with building and running the Fortran tests, 34 alongside the Fortran tests omit the `-DTEST_SUITE_SUBDIRS` CMake
33 i.e. it is not possible to only build and run the Fortran tests with 35 variable.
34 the exception of the [External
35 tests](https://llvm.org/docs/TestSuiteGuide.html#external-suites).
36 36
37 37
38 ## Running the SPEC CPU 2017 38 ## Running the SPEC CPU 2017
39 39
40 We recently added CMake hooks into the LLVM Test Suite to support 40 We recently added CMake hooks into the LLVM Test Suite to support