[Mpi-forum] 2nd vote Request for Fault Tolerance and Error Handling WG (ulfm part1)

Hello All, The Fault Tolerance and Error Handling WG would like to bring to a 2nd vote the fine-grain fault tolerance: process failure error semantics and revoke (aka ulfm part 1). Issue: https://github.com/mpi-forum/mpi-issues/issues/581 PR: https://github.com/mpi-forum/mpi-standard/pull/665

[Mpi-forum] Reading request for FT and ErrH WG: remove_error_class and related functions

Hello all, The Fault Tolerance and Error Handling WG would like to bring for a reading text adding the procedures to remove user-defined error classes, codes, and strings. Issue: https://github.com/mpi-forum/mpi-issues/issues/283 PR: https://github.com/mpi-forum/mpi-standard/pull/166 This is

[Mpi-forum] 1st vote request for Session WG issue related to clarifying error handling fallback

Hello All, I’d like to put in a request for a 1st vote During the upcoming Feb’23 MPI Forum: ## Clarification of errhandler fallback with Sessions Issue: https://github.com/mpi-forum/mpi-issues/issues/588 PR: https://github.com/mpi-forum/mpi-standard/pull/644 This issue adds clarifications

[Mpi-forum] Reading requests: Side-Documents and Deprecation of _X Procedures

Dear all, I would like to announce two readings for the February MPI Forum meeting. Introduce the concept of side documents Issue: https://github.com/mpi-forum/mpi-issues/issues/562 PR: https://github.com/mpi-forum/mpi-standard/pull/694 Deprecate all _x procedures Issue:

[Mpi-forum] Additional Reading #543 at MPI-Forum meeting Feb 1+8, 2023 (related to Terms and Contexts)

Dear MPI forum members, dear Wesley, I would like to have the following issue (and its PR) read: Issue 543 / PR791 "Pending operation" not defined, pending proper definition Issue https://github.com/mpi-forum/mpi-issues/issues/543 PR791 https://github.com/mpi-forum/mpi-standard/pull/791

Re: [Mpi-forum] why do we only support caching on win/comm/datatype?

Dan correctly interpreted my meaning. But Jeff is right that we should be modest. Tony Anthony Skjellum, PhD Professor of Computer Science and Chair of Excellence Director, SimCenter University of Tennessee at Chattanooga (UTC) tony-skjel...@utc.edu [or skjel...@gmail.com] cell:

Re: [Mpi-forum] why do we only support caching on win/comm/datatype?

Fair but let’s not try to boil the ocean and just start with ‘every object needs attributes’. The forum tends to be more successful with modestly scoped efforts. Sent from my iPhone > On 18. Jan 2023, at 19.40, Holmes, Daniel John > wrote: > >  > Hi all, > > I believe “orthogonality”

Re: [Mpi-forum] why do we only support caching on win/comm/datatype?

Hi all, I believe “orthogonality” here is intended to mean “every object needs this feature” rather than “every Forum member needs to be involved” (at least, I hope so). We have a single location for attributes-that-have-callbacks: section 7.7 in MPI-4.0 – although there are also window

Re: [Mpi-forum] why do we only support caching on win/comm/datatype?

This isn’t an orthogonality issues. The issue is not linear dependence of features but a null space caused by a surprising failure to pursue consistency in the attributes feature set. We have a chapter for attributes. I see no need for another WG to fix this. Sent from my iPhone > On 18. Jan

Re: [Mpi-forum] why do we only support caching on win/comm/datatype?

https://github.com/mpi-forum/mpi-issues/issues/667 https://github.com/mpi-forum/mpi-issues/issues/664 You should create a new issue for sessions attributes. We can merge into a single meta issue later if appropriate. Sent from my iPhone > On 18. Jan 2023, at 19.17, Koziol, Quincey via

Re: [Mpi-forum] why do we only support caching on win/comm/datatype?

We need a cross-cutting WG on "orthogonality" of feature set in MPI-5. Anthony Skjellum, PhD Professor of Computer Science and Chair of Excellence Director, SimCenter University of Tennessee at Chattanooga (UTC) tony-skjel...@utc.edu [or skjel...@gmail.com] cell: 205-807-4968

[Mpi-forum] Additional Reading #669 at MPI-Forum meeting Feb 1+8, 2023 (related to Terms)

Dear MPI forum members, dear Wesley, I would like to have the following issues (and their PRs) read. Issue 669 / PR788 Add operation state "enabled" and "local calls" into Terms Issue https://github.com/mpi-forum/mpi-issues/issues/669 PR788 https://github.com/mpi-forum/mpi-standard/pull/788

[Mpi-forum] No-no-vote / first vote: deprecate mpif.h

Dear all, I'd like to request a no-no-vote and first vote for the following ticket: *Deprecate mpif.h* Issue: https://github.com/mpi-forum/mpi-issues/issues/561 PR: https://github.com/mpi-forum/mpi-standard/pull/722 Changes since the last reading:

[Mpi-forum] MPI Forum Mailing List DNS Fixed

Hi all, As mentioned in the test message, the DNS records for the MPI Forum seem to have had a problem when we moved over to our new provider last month. It seems like things are working now, but it’s possible that you might have missed some recent messages (particularly if you use Gmail for

[Mpi-forum] Reading requests: language interoperability concerns

On behalf of JeffH I'd like to request a no-no reading and first vote for the following issues/PRs addressing language interoperability issues: *add MPI_Status_{set,get} for 3 status fields* Issue: https://github.com/mpi-forum/mpi-issues/issues/645 PR:

[Mpi-forum] No Virtual Meeting today / Deadline for announcements TODAY

Hi all, As discussed last week, there is no MPI virtual meeting today. However, please keep in mind that today is the deadline for all ballot and reading announcements for our next voting meeting, which will be February 1st and 8th. Thanks! Martin -- Prof. Dr. Martin Schulz,