mtl/ofi: Fix MPI_ANY_SOURCE for i(m)probe in v3.0.x #6191
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix invalid handling of MPI_ANY_SOURCE for i(m)probe by using the any_source address handle rather than the 0 address handle. Intel test cases MPI_Probe_source_c and MPI_Probe_tag_c now passes. Commit e667455 in master (which has the fix) was a feature change and we are just backporting the bug fix to 3.1.x and 3.0.x branches. Signed-off-by: Mohan Gandhi <[email protected]>
aravindksg
approved these changes
Dec 12, 2018
bwbarrett
approved these changes
Dec 13, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fix invalid handling of MPI_ANY_SOURCE for i(m)probe
by using the any_source address handle rather than
the 0 address handle. Intel test cases
MPI_Probe_source_c and MPI_Probe_tag_c now passes.
Commit e667455 in master (which has the fix) was a
feature change and we are just backporting the bug fix
to 3.1.x and 3.0.x branches.
Signed-off-by: Mohan Gandhi [email protected]