-
Notifications
You must be signed in to change notification settings - Fork 9
Closed
Labels
Chapter Committee ChangeChanges to be made by the respective chapter committee(s)Changes to be made by the respective chapter committee(s)[done] mpi-4.1For inclusion in the MPI 4.1 standardFor inclusion in the MPI 4.1 standardchap-topologiesProcess Topologies Chapter CommitteeProcess Topologies Chapter Committeehad readingCompleted the formal proposal readingCompleted the formal proposal readingscheduled readingReading is scheduled for the next meetingReading is scheduled for the next meeting
Milestone
Description
Problem
Example: page 412, code for MPI_NEIGHBOR_ALLGATHER
The code is supposed to be binding, but is pseudo code. How should this be handled? Should the code be complete and runnable? How to distinguish this from examples?
Proposal
tbd
Changes to the Text
tbd
Impact on Implementations
tbd
Impact on Users
tbd
References
Insert any internal (other issues) or external (websites, papers, etc.) references here.
Metadata
Metadata
Assignees
Labels
Chapter Committee ChangeChanges to be made by the respective chapter committee(s)Changes to be made by the respective chapter committee(s)[done] mpi-4.1For inclusion in the MPI 4.1 standardFor inclusion in the MPI 4.1 standardchap-topologiesProcess Topologies Chapter CommitteeProcess Topologies Chapter Committeehad readingCompleted the formal proposal readingCompleted the formal proposal readingscheduled readingReading is scheduled for the next meetingReading is scheduled for the next meeting