@@ -92,22 +92,28 @@ angular brackets (<>) denote a user-provided value, and passing a substring limi
9292the tests with test subjects or test descriptions containing the user-specified substring.
9393```
9494
95- ### Single-image (serial) testing with GNU Fortran (` gfortran ` )
95+ ### GNU Fortran (` gfortran ` ) compiler
96+ #### Single-image (serial) testing
9697With recent versions of [ GNU Fortran] (gfortran) and [ OpenCoarrays] installed,
9798execute the following command in a ` zsh ` or ` bash ` -like shell:
9899``` zsh
99100fpm test
100101```
101102
102- ### Multi-image (parallel) testing with ` gfortran ` and OpenCoarrays
103- With recent versions of [ GNU Fortran ] ( gfortran) and [ OpenCoarrays] installed,
103+ #### Multi-image (parallel) testing
104+ With recent versions of ` gfortran ` and [ OpenCoarrays] installed,
104105execute the following command in a ` zsh ` or ` bash ` -like shell:
105106``` zsh
106107fpm test --compiler caf --runner " cafrun -n 4"
107108```
108109Substitute the desired number of images for the ` 4 ` above.
109110
110- ### Testing with the Numerical Algorithms Group (` nagfor ` ) compiler
111+ ### Intel (` ifx ` ) compiler
112+ ``` zsh
113+ fpm test --compiler ifx --flag " -coarray"
114+ ```
115+
116+ ### Numerical Algorithms Group (` nagfor ` ) compiler
111117``` zsh
112118fpm test --compiler nagfor --flag -fpp
113119```
@@ -116,7 +122,7 @@ fpm test --compiler nagfor --flag -fpp
116122Because ` fpm ` uses the compiler name to determine the compiler identity and because
117123CCE provides one compiler wrapper, ` ftn ` , for invoking all compilers, you will
118124need to invoke ` ftn ` in a shell script named to identify CCE compiler. For example,
119- place a script named ` crayftn.sh ` in your path with the following contents and with
125+ place a script named ` crayftn.sh ` in your PATH with the following contents and with
120126executable privileges set appropriately:
121127```
122128#!/bin/bash
0 commit comments