MPI-4.1 announcements for Mar'23 voting meeting
Hi all, I'd like to announce a (re-)reading for the upcoming Mar'23 meeting. Issue: https://github.com/mpi-forum/mpi-issues/issues/639 PR: https://github.com/mpi-forum/mpi-standard/pull/750 Changes since last reading (basically a complete re-write of the affected sentence): https://github.com/mpi-forum/mpi-standard/pull/750/files/78353ac06a93a01db2d... PDF (with highlights, p68): https://github.com/mpi-forum/mpi-issues/files/10785518/mpi41-report_Issue639... I would also like to request a 2nd vote for the following issues that have passed a 1st vote: Issue: https://github.com/mpi-forum/mpi-issues/issues/188 PR: https://github.com/mpi-forum/mpi-standard/pull/203 Summary: state that Example 3.10 is unsafe Issue: https://github.com/mpi-forum/mpi-issues/issues/83 PR: https://github.com/mpi-forum/mpi-standard/pull/666 Summary: new Info key for strict start order of persistent collective operations Issue: https://github.com/mpi-forum/mpi-issues/issues/472 PR: https://github.com/mpi-forum/mpi-standard/pull/606 Summary: disambiguate "rank" in the point-to-point chapter Issue: https://github.com/mpi-forum/mpi-issues/issues/117 PR: https://github.com/mpi-forum/mpi-standard/pull/748 Summary: "logically concurrent" might not be - advice All these are unchanged since their 1st vote state. Best wishes, Dan.
participants (1)
-
Holmes, Daniel John