|
2 | 2 |
|
3 | 3 | # Machines
|
4 | 4 |
|
5 |
| -Polaris attempts to be aware of the capabilities of the machine it is running |
6 |
| -on. This is a particular advantage for so-called "supported" machines with a |
7 |
| -config file defined for them in the `polaris` package. But even for "unknown" |
8 |
| -machines, it is not difficult to set a few config options in your user config |
9 |
| -file to describe your machine. Then, polaris can use this data to make sure |
| 5 | +Polaris attempts to be aware of the capabilities of the machine it is running |
| 6 | +on. This is a particular advantage for so-called "supported" machines with a |
| 7 | +config file defined for them in the `polaris` package. But even for "unknown" |
| 8 | +machines, it is not difficult to set a few config options in your user config |
| 9 | +file to describe your machine. Then, polaris can use this data to make sure |
10 | 10 | test cases are configured in a way that is appropriate for your machine.
|
11 | 11 |
|
12 | 12 | (dev-supported-machines)=
|
@@ -57,6 +57,8 @@ supported for those configurations with `gnu` compilers.
|
57 | 57 | | compy | intel | impi | intel-mpi |
|
58 | 58 | +--------------+------------+-----------+-------------------+
|
59 | 59 | | pm-cpu | gnu | mpich | gnu-cray |
|
| 60 | +| +------------+-----------+-------------------+ |
| 61 | +| | intel | mpich | intel-cray | |
60 | 62 | +--------------+------------+-----------+-------------------+
|
61 | 63 | ```
|
62 | 64 |
|
@@ -288,8 +290,8 @@ spack:
|
288 | 290 | modules: []
|
289 | 291 | environment: {}
|
290 | 292 | extra_rpaths: []
|
291 |
| -``` |
292 |
| - |
| 293 | +``` |
| 294 | +
|
293 | 295 | Typically your system will already have compilers if nothing else, and this is
|
294 | 296 | what we assume here. Give the appropriate path (replace `/usr` with the
|
295 | 297 | appropriate path on your system). We have had better luck with `gcc` than
|
|
0 commit comments