Skip to content

Update Syntax paper to match 25-165r1 #6

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

Merged
merged 2 commits into from
Oct 20, 2025
Merged

Update Syntax paper to match 25-165r1 #6

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2940f88
Update references
bonachea Oct 17, 2025
e0bf268
Update Completion Subroutine Syntax
bonachea Oct 17, 2025
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
47 changes: 15 additions & 32 deletions drafts/draft-syntax.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,17 +2,17 @@ To: J3 J3/25-166
Subject: US04: Syntax for Asynchronous Collective Subroutines
From: Brandon Cook & Damian Rouson & Dan Bonachea & Reuben D. Budiardja
Date: 2025-September-12
References: J3/25-162r1, J3/25-165, J3/25-127r1, WG5/N2249
References: J3/25-162r2, J3/25-165r1, J3/25-127r1, WG5/N2249

1. Background
-------------
The current Fortran 202Y work list WG5/N2249 includes asynchronous
collective subroutines as accepted work item US04.

Paper J3/25-162r1 "US04: Requirements for Asynchronous Collective
Paper J3/25-162r2 "US04: Requirements for Asynchronous Collective
Subroutines" presents an illustrative use case and a list of requirements.

Paper J3/25-165 "US04: Specifications for Asynchronous Collective
Paper J3/25-165r1 "US04: Specifications for Asynchronous Collective
Subroutines" presents the proposed specifications and semantics for the new
asynchronous collective subroutines feature. Please consult that paper for
all semantic details, which will not be replicated here.
Expand All @@ -26,7 +26,7 @@ for the asynchronous collective subroutines feature.
T1. New type COMPLETION_TYPE is added to the ISO_FORTRAN_ENV intrinsic
module.

See J3/25-165 for detailed specifications and semantics.
See J3/25-165r1 for detailed specifications and semantics.

3. Asynchronous Collective Initiation Syntax
--------------------------------------------
Expand All @@ -45,7 +45,7 @@ C4. CO_REDUCE (A, OPERATION [, RESULT_IMAGE, STAT, ERRMSG, COMPLETION])

C5. CO_SUM (A [, RESULT_IMAGE, STAT, ERRMSG, COMPLETION])

See J3/25-165 for detailed specifications and semantics.
See J3/25-165r1 for detailed specifications and semantics.

Note that J3/25-127r1 "DIN1: Collectives over a specified team,
req/spec/syntax/edits" also adds a different trailing optional argument
Expand All @@ -58,39 +58,22 @@ C6. Assuming that edits for both work items DIN1 and US04 are applied for
immediately precede the new optional COMPLETION argument in the syntax
of each collective subroutine listed above.

4. Completion Wait Statement Syntax
4. Completion Query Function Syntax
-----------------------------------

A new <action-stmt> called COMPLETION WAIT is introduced, with the
A new standard intrinsic subroutine called COMPLETE is introduced, with the
following syntax:

W1. <completion-wait-stmt> <<is>>
COMPLETION WAIT ( <completion-item> )
W1. COMPLETE( COMPLETION_VAR [, QUERY ])

W2. <completion-item> <<is>> <variable>
W2. COMPLETION_VAR shall be a variable of type COMPLETION_TYPE from the
intrinsic module ISO_FORTRAN_ENV. It shall not be
coindexed. It is an INTENT(INOUT) argument.

W3. The <completion-item> specifier to COMPLETION WAIT shall be a variable
of type COMPLETION_TYPE from the intrinsic module ISO_FORTRAN_ENV.
W3. QUERY (optional) when present, shall be a variable of logical type with
the same shape as COMPLETION_VAR. It is an INTENT(OUT)
argument.

W4. The COMPLETION WAIT statement contains no specifiers other than the
<completion-item>.

See J3/25-165 for detailed specifications and semantics.

5. Completion Query Function Syntax
-----------------------------------

A new standard intrinsic elemental function called COMPLETION_QUERY is
introduced, with the following syntax:

Q1. COMPLETION_QUERY ( COMPLETION )

Q1. The COMPLETION argument to COMPLETION_QUERY() shall be a variable of
type COMPLETION_TYPE from the intrinsic module ISO_FORTRAN_ENV.

Q3. The COMPLETION_QUERY function accepts no arguments other than the
completion variable.

See J3/25-165 for detailed specifications and semantics.
See J3/25-165r1 for detailed specifications and semantics.

===END===