fix explanation of in-place option for MPI_Allgather(v) #12729
Merged
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.
These man pages (for
MPI_Allgather
andMPI_Allgatherv
when usingMPI_IN_PLACE
) were wrong (intended to callMPI_Gather(v)
). The example is a bit confusing becauserecvbuf
is modified in a loop of repeat calls, but I think the loop is still correct because the subset ofrecvbuf
that acts as send area when usingMPI_IN_PLACE
should be invariant. I don't know if you want to keep this explanation; it certainly can't be used to explain sibling collectives that supportMPI_IN_PLACE
.(Apologies for the incorrect explanation prior to edit.)