Skip to content

v3.1: Fix a corner case for the datatype extent computation. #6901

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 20, 2019

Conversation

bosilca
Copy link
Member

@bosilca bosilca commented Aug 14, 2019

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 [email protected]

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 <[email protected]>
@bwbarrett
Copy link
Member

@bosilca does this also need to go to 3.0?

@jsquyres jsquyres added this to the v3.1.5 milestone Aug 20, 2019
@jsquyres jsquyres changed the title Fix a corner case for the datatype extent computation. v3.1: Fix a corner case for the datatype extent computation. Aug 20, 2019
@jsquyres jsquyres merged commit cd34c72 into open-mpi:v3.1.x Aug 20, 2019
@jsquyres jsquyres added the NEWS label Aug 20, 2019
@jsquyres
Copy link
Member

@bwbarrett The commit cherry-picked cleanly to the v3.0.x branch, so I took the liberty of creating the v3.0.x PR for this: #6913

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants