Undo work-around for Conduit limitation. #1329
Merged
Conversation
This file contains 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
In earlier versions, Conduit used to not support MPI_ANY_SOURCE and MPI_ANY_TAG when checking non-blocking sends and receives. It does now.
gunney1
requested review from
cyrush,
BradWhitlock,
kennyweiss,
rhornung67,
publixsubfan,
agcapps and
bmhan12
agcapps
approved these changes
Apr 26, 2024
cyrush
approved these changes
Apr 29, 2024
white238
approved these changes
Apr 29, 2024
rhornung67
approved these changes
Apr 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In earlier versions, Conduit used to not support MPI_ANY_SOURCE and MPI_ANY_TAG when checking non-blocking sends and receives. It does now.
This change backs out a work-around I implemented at the time.