Skip to content

v3.0.x: datatype_optimize: keep 0-extent instances #7024

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

Conversation

jsquyres
Copy link
Member

Do not remove 0-extent instances while optimizing the datatype. This
is a distillation of a larger set of DDT bug fixes and optimizations
from master. George tried to cherry-pick these fixes+optimizations
back to the v3.0.x/v3.1.x branches and it resulted in a giant list of
heavily-modified cherry-picked commits (see
#6978). This did not seem like a
good idea.

George therefore distilled the critical bug fix down to this small
commit, suitable for both the v3.0.x/v3.1.x branches. See
#7019 (comment)
for details.

Signed-off-by: Jeff Squyres [email protected]
(cherry picked from commit b77ee56)

Refs #7019

Do not remove 0-extent instances while optimizing the datatype.  This
is a distillation of a larger set of DDT bug fixes and optimizations
from master.  George tried to cherry-pick these fixes+optimizations
back to the v3.0.x/v3.1.x branches and it resulted in a giant list of
heavily-modified cherry-picked commits (see
open-mpi#6978).  This did not seem like a
good idea.

George therefore distilled the critical bug fix down to this small
commit, suitable for both the v3.0.x/v3.1.x branches.  See
open-mpi#7019 (comment)
for details.

Signed-off-by: Jeff Squyres <[email protected]>
(cherry picked from commit b77ee56)
@jsquyres jsquyres added the NEWS label Oct 1, 2019
@jsquyres jsquyres merged commit 2d6e64d into open-mpi:v3.0.x Oct 1, 2019
@jsquyres jsquyres deleted the pr/v3.0.x/small-ddt-optimization-fix branch October 1, 2019 13:21
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.

2 participants