v3.0.x: Fix a corner case for the datatype extent computation. #6913
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
It turns out that if a complex datatype built out of a single predefined type has been resized to the size of its predefined type, we miscompute the extent when creating other datatypes with the type. Provides a fix for open-mpi#6899 for the 3.x branch. Signed-off-by: George Bosilca <bosilca@icl.utk.edu> (cherry picked from commit f09d011)
This was referenced Aug 20, 2019
bosilca
approved these changes
Aug 20, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
It turns out that if a complex datatype built out of a single predefined
type has been resized to the size of its predefined type, we miscompute
the extent when creating other datatypes with the type.
Provides a fix for #6899 for the 3.x branch.
Signed-off-by: George Bosilca bosilca@icl.utk.edu
(cherry picked from commit f09d011)
NOTE: This was cherry-picked from the v3.1.x branch because that commit was specially crafted for the v3.x branches (i.e., it didn't come directly from master).