diff options
| author | Axel Huebl <axel.huebl@plasma.ninja> | 2021-06-24 21:44:21 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2021-07-13 13:47:51 (GMT) |
| commit | d9fcbb06f2e39b5290f22ebc0e2c5076ae026ccd (patch) | |
| tree | 4e403692f3f16f670c6b211b5bd18a61c2d4a135 /Tests/Module/WriteCompilerDetectionHeader/multi_files.cpp | |
| parent | 460e812369db398da34e14c9d40c3ecec06afaf1 (diff) | |
| download | CMake-d9fcbb06f2e39b5290f22ebc0e2c5076ae026ccd.zip CMake-d9fcbb06f2e39b5290f22ebc0e2c5076ae026ccd.tar.gz CMake-d9fcbb06f2e39b5290f22ebc0e2c5076ae026ccd.tar.bz2 | |
FindMPI: Interrogate Cray compiler
Cray traditionally does not ship mpicc/mpic++ compiler wrappers.
Due to that, the traditional CMake logic to find MPI is to *only*
support MPI on Cray systems if either
1. Cray Wrappers are used for compiling, or
2. an auxiliary MPI executable is found.
On many new Exascale prototypes, using the Cray wrappers for develop
work is extremely painful. Vendors such as AMD and integrators such
as HPE seem not to go well in lock-step in Cray programming envs,
making offloading with Cray wrappers too challenging. On the other
hand, using the working experimental Vendor compilers works well,
as long as one does not need MPI.
Extend the fallback MPI search logic by also interrogating the
CC/cc/ftn binaries if found for their MPI flags. This does not
change existing logic, i.e. using the Cray wrappers directly, but
provides an additional way to get MPI programs compiled on Cray.
Fixes: #22368
Diffstat (limited to 'Tests/Module/WriteCompilerDetectionHeader/multi_files.cpp')
0 files changed, 0 insertions, 0 deletions