forked from open-mpi/ompi
-
Notifications
You must be signed in to change notification settings - Fork 2
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
sessions - need some changes concerning MPI_MAX_FROM_GROUP_STRINGTAG, etc #37
Comments
hppritcha
added a commit
that referenced
this issue
Jun 9, 2021
per the MPI 4.0 standard related to #37 Signed-off-by: Howard Pritchard <howardp@lanl.gov>
closed via 23c5c0d |
hppritcha
added a commit
that referenced
this issue
Jun 16, 2021
per the MPI 4.0 standard related to #37 Signed-off-by: Howard Pritchard <howardp@lanl.gov>
hppritcha
added a commit
that referenced
this issue
Jul 6, 2021
per the MPI 4.0 standard related to #37 Signed-off-by: Howard Pritchard <howardp@lanl.gov>
hppritcha
added a commit
that referenced
this issue
Aug 4, 2021
per the MPI 4.0 standard related to #37 Signed-off-by: Howard Pritchard <howardp@lanl.gov>
hppritcha
added a commit
that referenced
this issue
Nov 20, 2021
per the MPI 4.0 standard related to #37 Signed-off-by: Howard Pritchard <howardp@lanl.gov>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the MPI forum week of 12/7/20 issues with the MPI_MAX_FROM_GROUP_TAG/STRINGTAG were uncovered. First there was an error in the standard release candidate and we will only be using MPI_MAX_FROM_GROUP_STRINGTAG going forward.
More importantly for the prototype, we need to add some kind of check either at run or compile time to verify that this constant is checked against the PMIx the PMIX_MAX_NSLEN constant.
The text was updated successfully, but these errors were encountered: