Hello all together, As Language Bindings Summary Chapter, I'd like to read the following issues at the next meeting (Dec. 2022).
The Annex A.2 was developed by Terms WG as proof of new Semantic Terms section 2.4 for MPI-4.0 and also as a very helpful summary for the reader of the MPI standard. Puri Bangalore converted it into Latex, Joseph Schuchart helped to add the RMA chapter, and other smaller issues, and the forum commented on it at the virtual meeting Nov. 9, 2022. The forum asked for moving it into a side-doc as long as it is incomplete. The following issues and pull requests are completing the side-document Annex A.2 and moving it back to the MPI-standard. Completing the side-doc: - Issue A.2-#17: https://github.com/mpi-forum/function-table/issues/17 PR: https://github.com/mpi-forum/function-table/pull/9 Adding all operation related routines for one-sided communication - Issue A.2-#5: https://github.com/mpi-forum/function-table/issues/5 PR: https://github.com/mpi-forum/function-table/pull/14 Adding MPI_Comm_set_info - Issue A.2-#7: https://github.com/mpi-forum/function-table/issues/7 PR: https://github.com/mpi-forum/function-table/pull/15 Correction for MPI_COMM_CREATE, ... (a missing f in the table entry) - Issue A.2-#8: https://github.com/mpi-forum/function-table/issues/8 PR: https://github.com/mpi-forum/function-table/pull/12 Removing wrong remark 4) on the NEIGHBOR-routines - Issue A.2-#10: https://github.com/mpi-forum/function-table/issues/10 PR: https://github.com/mpi-forum/function-table/pull/16 Adding MPI_Cancel and MPI_Test_cancelled - Issue A.2-#11: https://github.com/mpi-forum/function-table/issues/11 PR: https://github.com/mpi-forum/function-table/pull/13 Adding an intro sentence that often procedures are presented under constrains And then moving the side-doc into MPI-4.1: - Issue #641: https://github.com/mpi-forum/mpi-issues/issues/641 PR: https://github.com/mpi-forum/mpi-standard/pull/752 Integrating the content of the side-doc https://www.mpi-forum.org/docs/mpi-4.0/addendum-Semantics.pdf plus all the issues above into MPI-4.1 The whole Annex A.2 including all these PRs can be viewed as commented pdf: - PDF, see pages 11, 839-846 and 1007: https://github.com/mpi-forum/mpi-standard/files/10031494/mpi41-report_Issue641_PR752.pdf It includes PR752 and all the Annex A.2 side-doc pull requests A.2-PR9, A.2-PR12, A.2-PR13, A.2-PR14, A.2-PR15, and A.2-PR16. All the other issues (493, 499, 468, 565, 471, 605, 556) and probably chapter committee changes (412, 420, 492, 560) see below in my email from yesterday. Best regards Rolf ----- Original Message ----- > To: "Main MPI Forum mailing list" <mpi-forum@lists.mpi-forum.org> > Cc: "Rolf Rabenseifner" <rabenseif...@hlrs.de> > Sent: Wednesday, November 16, 2022 11:44:48 PM > Subject: [Mpi-forum] Reading and voting announcement > Hello all, > > As the Chapter Committee or WG chair or member, or ticket owner, > I'd like to read the following items at the next meeting (Dec. 2022): > > Readings about the Progress rules: > > - Issue #493: https://github.com/mpi-forum/mpi-issues/issues/493 > PR: https://github.com/mpi-forum/mpi-standard/pull/753 > PDF: > > https://github.com/mpi-forum/mpi-standard/files/10016623/mpi41-report_Issue493_PR753.pdf > > Issue: New Section "2.9 Progress" in the Terms-Chapter > + additional rule and example 12.13 in Section "12.7.3 Progress" > > The proposal was developed by Dan Holmes, Claudia Blaas-Schenner, Joseph > Schuchart, > Tobias Haas, and myself with additional support from Bill Gropp and many > forum > members > during the discussions for MPI-4.0 and at the virtual MPI-4.1 meeting on > Nov. 2, > 2022. > > > - Issue #499: https://github.com/mpi-forum/mpi-issues/issues/499 > PR: https://github.com/mpi-forum/mpi-standard/pull/729 > PDF: > > https://github.com/mpi-forum/mpi-standard/files/10024194/mpi41-report_Issue499_PR729.pdf > see page pages 569 and 999 > > Issue: Explicit progress rule for MPI_WIN_TEST > > - Related Issue #468 (MPI_REQUEST_GET_STATUS) and #492 (some wording) see > below. > > > Reading about Annex A.2 (semantic of operation-related MPI procedures) > > - will be announced tomorrow (Issue #641 and PR752) > > > Other readings: > > - Issue #565: https://github.com/mpi-forum/mpi-issues/issues/565 > PR: https://github.com/mpi-forum/mpi-standard/pull/727 > > Issue: Fortran 2018 instead or additional to TS 29113 > (by Jeff Hammond) > In Terms and Language Binding chapters > > > Reading + Issue-0 voting > ------------------------ > > - Issue #471: https://github.com/mpi-forum/mpi-issues/issues/471 > PR: https://github.com/mpi-forum/mpi-standard/pull/751 > Content: tasks --> MPI processes in Terms chapter > reading + ticket-0-voting > > > - Issue #605: https://github.com/mpi-forum/mpi-issues/issues/605 > PR: https://github.com/mpi-forum/mpi-standard/pull/746 > PDF: > > https://github.com/mpi-forum/mpi-standard/files/10024811/mpi41-report_Issue605_PR746.pdf > > Issue: Title-lines/sentences for all examples in the "Topologies" chapter > > > Errata reading and voting > ------------------------- > > - Issue #556: https://github.com/mpi-forum/mpi-issues/issues/556 > PR: https://github.com/mpi-forum/mpi-standard/pull/690 > > Issue: Reverting unintended change of the definition of > the coords argument in MPI_CART_COORDS > (Issue is by Kyle Gerard Felker, PR by Christoph Niethammer) > > > 1st vote is scheduled for > ------------------------- > > - Issue #468: https://github.com/mpi-forum/mpi-issues/issues/468 > PR: https://github.com/mpi-forum/mpi-standard/pull/667 > > Issue: Explicit progress rule for MPI_REQUEST_GET_STATUS > > > In addition, I'd like to read the following items at the Dec. 2022 forum > meeting > if they are not yet passed as chapter committee change. > > If they pass as chapter committee change, then please take this > only as a notice about those changes: > > - Issue #412: https://github.com/mpi-forum/mpi-issues/issues/412 > PR: https://github.com/mpi-forum/mpi-standard/pull/743 > PDF: > > https://github.com/mpi-forum/mpi-standard/files/10023828/mpi41-report_Issue412_PR743.pdf > > - Issue #420: https://github.com/mpi-forum/mpi-issues/issues/420 > PR: https://github.com/mpi-forum/mpi-standard/pull/745 > PDF: > > https://github.com/mpi-forum/mpi-standard/files/10023634/mpi41-report_Issue420_PR745.pdf > > - Issue #492: https://github.com/mpi-forum/mpi-issues/issues/492 > PR: https://github.com/mpi-forum/mpi-standard/pull/672 > no PDF, because trivial > > - Issue #560: https://github.com/mpi-forum/mpi-issues/issues/560 > PR: https://github.com/mpi-forum/mpi-standard/pull/713 > PDF: > > https://github.com/mpi-forum/mpi-standard/files/10023611/mpi41-report_Issue560_PR713.pdf > > > Best regards > Rolf -- Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseif...@hlrs.de . High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . Nobelstr. 19, 70569 Stuttgart, Germany _______________________________________________ mpi-forum mailing list mpi-forum@lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpi-forum
