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.

Sign up for GitHub

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

Jump to bottom

[SHMEM 1.6rc2 Sec 9.1-9.3] Clarification of team_ptr with TEAM_WORLD and multi-init with different thread levels #548

Merged
merged 2 commits into from
Nov 1, 2024
Merged

[SHMEM 1.6rc2 Sec 9.1-9.3] Clarification of team_ptr with TEAM_WORLD and multi-init with different thread levels #548

merged 2 commits into from
Nov 1, 2024

Conversation

wrrobin
Copy link
Collaborator

@wrrobin wrrobin commented Oct 3, 2024

Summary of changes

This PR addresses #541 and also clarifies that shmem_team_ptr behavior is same as shmem_ptr when the team argument equals SHMEM_TEAM_WORLD.

Proposal Checklist

  • Link to issue(s)
  • Changelog entry
  • Reviewed for changes to front matter
  • Reviewed for changes to back matter

jdinan
jdinan reviewed Oct 3, 2024
View reviewed changes
content/threads_intro.tex Outdated Show resolved Hide resolved
@jdinan jdinan added this to the OpenSHMEM 1.6 milestone Oct 10, 2024
@jdinan jdinan changed the title [SHMEM 1.6rc1 Sec 9.1-9.3] Clarification of team_ptr with TEAM_WORLD and multi-init with different thread levels [SHMEM 1.6rc2 Sec 9.1-9.3] Clarification of team_ptr with TEAM_WORLD and multi-init with different thread levels Oct 10, 2024
@jdinan jdinan mentioned this pull request Oct 11, 2024
Merged
@jdinan jdinan merged commit 7219015 into openshmem-org:master Nov 1, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jdinan jdinan jdinan left review comments

Assignees
No one assigned
Labels
SectionCommittee
Projects
No open projects
OpenSHMEM 1.6 Section Committees
Status: Setup, Thrds, Mem (9.1-9.3)
Milestone
OpenSHMEM 1.6
Development

Successfully merging this pull request may close these issues.
2 participants
@wrrobin @jdinan