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

[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

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7360ca1
Unresolved issues of team_ptr and multi-init
wrrobin Oct 3, 2024
aa875fd
Update content/threads_intro.tex
wrrobin Oct 3, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions content/shmem_team_ptr.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,9 @@
when it can be accessed using memory loads and stores. Otherwise, a null
pointer is returned.

If \VAR{team} compares equal to \LibConstRef{SHMEM\_TEAM\_WORLD}, then
the behavior is identical to that of \FUNC{shmem\_ptr} with same \VAR{dest}
and \VAR{pe} arguments.
If \VAR{team} compares equal to \LibConstRef{SHMEM\_TEAM\_INVALID},
then a null pointer is returned.
If \VAR{team} is otherwise invalid, the behavior is undefined.
Expand Down
8 changes: 4 additions & 4 deletions content/threads_intro.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,10 +29,10 @@

\begin{enumerate}
\item
In the \CONST{SHMEM\_THREAD\_FUNNELED}, \CONST{SHMEM\_THREAD\_SERIALIZED}, and
\CONST{SHMEM\_THREAD\_MULTIPLE} thread levels, the \FUNC{shmem\_init\_thread} and
\FUNC{shmem\_finalize} calls must be invoked by the same thread.

In the \CONST{SHMEM\_THREAD\_FUNNELED} and \CONST{SHMEM\_THREAD\_SERIALIZED}
thread levels, all invocations of \FUNC{shmem\_init\_thread} and
\FUNC{shmem\_finalize} must be made by the same thread.
wrrobin marked this conversation as resolved.
Show resolved Hide resolved
\item
Any \openshmem operation initiated by a thread is considered an action of the
\ac{PE} as a whole. The symmetric heap and symmetric variables scope are not
Expand Down