Skip to content

opal/datatype: correctly handle large datatypes - v4.0 #6467

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

Closed
wants to merge 3 commits into from

Conversation

hoopoepg
Copy link
Contributor

@hoopoepg hoopoepg commented Mar 6, 2019

Always use size_t (instead of converting to an uint32_t) in order to
correctly support large datatypes.

backport from #6029

Refs #6016

ggouaillardet and others added 3 commits March 6, 2019 09:06
Always use size_t (instead of converting to an uint32_t) in order to
correctly support large datatypes.

Thanks Ben Menadue for the initial bug report

Refs open-mpi#6016

Signed-off-by: Gilles Gouaillardet <[email protected]>
(cherry picked from commit fbb5bb8)

Conflicts:
	opal/datatype/opal_convertor_raw.c
Signed-off-by: George Bosilca <[email protected]>
(cherry picked from commit 88a693b)

Conflicts:
	test/datatype/Makefile.am
Signed-off-by: George Bosilca <[email protected]>
(cherry picked from commit 1d8ad92)
@hoopoepg hoopoepg closed this Mar 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants