File tree Expand file tree Collapse file tree 1 file changed +10
-10
lines changed Expand file tree Collapse file tree 1 file changed +10
-10
lines changed Original file line number Diff line number Diff line change @@ -21,18 +21,18 @@ code-generation capabilities.
21
21
22
22
Fortran support can be enabled by setting the following CMake variables:
23
23
```
24
- % cmake -DCMAKE_Fortran_COMPILER=<path to Fortran compiler> \
25
- -DTEST_SUITE_FORTRAN:STRING=ON \
26
- -C../test-suite/cmake/caches/O3.cmake \
27
- ../test-suite
24
+ cmake -G "Ninja" -DCMAKE_C_COMPILER=<path to C compiler> \
25
+ -DCMAKE_CXX_COMPILER=<path to C++ compiler> \
26
+ -DCMAKE_Fortran_COMPILER=<path to Fortran compiler> \
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
31
- shortcoming in the design of the test suite is that building the C/C++
32
- tests is conflated with building and running the Fortran tests,
33
- i.e. it is not possible to only build and run the Fortran tests with
34
- the exception of the [ External
35
- tests] ( https://llvm.org/docs/TestSuiteGuide.html#external-suites ) .
32
+ This will configure the test-suite to run only the Fortran tests which
33
+ are found in the Fortran subdirectory. To run the C/C++ tests
34
+ alongside the Fortran tests omit the ` -DTEST_SUITE_SUBDIRS ` CMake
35
+ variable.
36
36
37
37
38
38
## Running the SPEC CPU 2017
You can’t perform that action at this time.
0 commit comments