Skip to content
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

Clarify return value for team split on SHMEM_TEAM_INVALID #461

Merged
merged 5 commits into from
Nov 9, 2021

Conversation

davidozog
Copy link
Collaborator

This PR is meant to address #450 (as well as Sandia-OpenSHMEM/SOS#969 and Sandia-OpenSHMEM/SOS#972).

I don't believe 8b44a29 is a semantic change - just a clarification that a split operation on a SHMEM_TEAM_INVALID parent is indeed considered "unsuccessful" and the routine should return a nonzero value.

I also included a small change to the 2D team split example code (ec66ff2). This has no effect on the example, but leaving these variables uninitialized commonly causes a compiler warning. Please let me know if you prefer this in a separate PR...

Specifically, team split operations should return nonzero if the
parent_team argument is SHMEM_TEAM_INVALID.  This is likely not a
semantic change, just a clarification.

Signed-off-by: David M. Ozog <[email protected]>
@davidozog
Copy link
Collaborator Author

@jdinan and @manjugv - should this ticket have an official reading? I think it's not needed, but am happy to do it.

I also just realized the ec66ff2 commit is already approved in #449 but was never merged.

@jdinan
Copy link
Collaborator

jdinan commented Apr 22, 2021

@davidozog Thanks for keeping track of this ticket. This feels more significant than a doc edit to me. Given that we have the time, I would prefer to read this and give the committee a chance to weigh in on whether the case that's being clarified is one where the function should return nonzero.

@davidozog
Copy link
Collaborator Author

@jdinan - sure. Maybe I can do an unofficial reading at the upcoming meeting to see if it generates any concerns. It's too late to announce an official reading this time...

@davidozog
Copy link
Collaborator Author

Note - this should go into errata (and/or pending errata?)

Also need a changelog entry.

@davidozog
Copy link
Collaborator Author

@jdinan - I was about to cherry-pick 503317b from @kholland-intel's PR, which adds a v1.6 change-log that mentions shmem_team_ptr. Is that ok, or would you prefer a separate change-log commit on this PR that might conflict later?

@jdinan
Copy link
Collaborator

jdinan commented Sep 20, 2021

@davidozog Please go ahead and add a changelog entry to the effect of "Clarified the return value of team split operations when the parent team is SHMEM_TEAM_INVALID". In the future, I'd prefer to include the changelog entry with the reading since it will help with consistency.

Please don't cherry pick from another PR. I'll deal with any merge conflicts as they come up.

@jdinan
Copy link
Collaborator

jdinan commented Sep 20, 2021

@davidozog The changelog heading in question was merged into master. Please merge from master and add your changelog entry.

@jdinan
Copy link
Collaborator

jdinan commented Sep 30, 2021

@davidozog Could you please review the changelog entry in 75559f8?

@davidozog
Copy link
Collaborator Author

davidozog commented Oct 1, 2021

@jdinan - 75559f8 looks great, and thanks for merging this with master. And I'm so sorry for the delay!

@davidozog
Copy link
Collaborator Author

@jdinan - I believe this PR is ready to merge. Is there anything pending on your end?

(This should close Sandia-OpenSHMEM/SOS#969)

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