diff options
| author | Christian Pfeiffer <cpfeiffer@live.de> | 2017-10-24 14:14:14 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2017-10-24 14:41:02 (GMT) |
| commit | 1610f757aca30ec2228e6cb9286338264f032545 (patch) | |
| tree | efc34605550962dd5c54966c3c9dd5e6fdb929ef /Source/cmConfigureFileCommand.cxx | |
| parent | a91eb5e41f486628910f189bf40403568af013c7 (diff) | |
| download | CMake-1610f757aca30ec2228e6cb9286338264f032545.zip CMake-1610f757aca30ec2228e6cb9286338264f032545.tar.gz CMake-1610f757aca30ec2228e6cb9286338264f032545.tar.bz2 | |
FindMPI: Use physical cores for MPIEXEC_MAX_NUMPROCS
Since commit v3.9.0-rc1~224^2~1 (FindMPI: MPIEXEC handling improvements,
2017-04-21) the `ProcessorCount` module is being used to initialize
`MPIEXEC_MAX_NUMPROCS`. However, this leads to the logical cores being
counted rather than the physical ones, and some MPI implementations like
OpenMPI will error if mpiexec is called with that number. Switch it to
the number of physical cores using `cmake_host_system_information`.
This ensures that if `MPIEXEC_MAX_NUMPROCS` is being used to set up MPI
tests with CTest or similar that the tests won't spuriously fail due to
OpenMPI refusing to start the application.
Diffstat (limited to 'Source/cmConfigureFileCommand.cxx')
0 files changed, 0 insertions, 0 deletions