[Mpi-forum] FTWG Readings for December 2019

[Wesley Bland]

Hi all,

The Fault Tolerance Working Group would like to announce the following items for the Albuquerque meeting:

Readings

Issue 143 - Create MPI_INFO_ENV before MPI_INIT
Issue: https://github.com/mpi-forum/mpi-issues/issues/143 <https://github.com/mpi-forum/mpi-issues/issues/143>
Pull Request: https://github.com/mpi-forum/mpi-standard/pull/126 <https://github.com/mpi-forum/mpi-standard/pull/126>
Description: This proposes a new function called MPI_INFO_ENV_CREATE_ARGV which would allow the user to pass in the argc and argv parameters and receive an MPI_INFO_ENV-like object back, which could be used for all of the same functionality as MPI_INFO_ENV.

Second Vote

Issue 134 - Add MPI_ERR_PROC_ABORTED
Issue: https://github.com/mpi-forum/mpi-issues/issues/134 <https://github.com/mpi-forum/mpi-issues/issues/134>
Pull Request: https://github.com/mpi-forum/mpi-standard/pull/112 <https://github.com/mpi-forum/mpi-standard/pull/112>
Description: The proposal adds the MPI_ERR_PROC_ABORTED error class, that can be returned by operations that fail due to an aborted process.

Errata

Issue 152 - Make error code functions thread-safe
Issue: https://github.com/mpi-forum/mpi-issues/issues/152 <https://github.com/mpi-forum/mpi-issues/issues/152>
Pull Request: https://github.com/mpi-forum/mpi-standard/pull/141 <https://github.com/mpi-forum/mpi-standard/pull/141>
Description: Add MPI_ERROR_CLASS and MPI_ERROR_STRING to the list of always thread-safe functions.

Thanks,
Wesley
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpi-forum.org/pipermail/mpi-forum/attachments/20191125/10749bfb/attachment.html>