mpichversion: Adding feature string for GPU support for easy detection #7226
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Description
This PR add new feature strings to
mpichversion
for the GPU support. MPICH built with CUDA, HIP or ZE support will show cuda, hip or ze in the MPICH Features ofmpichversion
. This allow external tools to easily check for GPU support of the library.This PR also change the configure of MPICH test suite to detect if the MPICH library passed in
--with-mpi=
actually have GPU support before checking the availability of corresponding GPU libraries. Previously, the configure of the test suite will check and configure for GPU support even if the MPI does not support GPU (never checked). This leads to failure on sunspot with CPU-only MPICH build. Because ZE library is always present, the test suite will be configured with ZE support while a CPU-only MPICH is provided. The benchmark will failed at runtime due to unable to loadlibze_loader.so
.Author Checklist
Particularly focus on why, not what. Reference background, issues, test failures, xfail entries, etc.
Commits are self-contained and do not do two things at once.
Commit message is of the form:
module: short description
Commit message explains what's in the commit.
Whitespace checker. Warnings test. Additional tests via comments.
For non-Argonne authors, check contribution agreement.
If necessary, request an explicit comment from your companies PR approval manager.