MPI Forum ticket #357

gistfile1.diff

Index: chap-ei/ei-2.tex
===================================================================
--- chap-ei/ei-2.tex	(revision 1970)
+++ chap-ei/ei-2.tex	(working copy)
@@ -629,6 +629,8 @@
 thread is executing one of these routines, if another concurrently
 running thread also makes an MPI call, the outcome will be as if the
 calls executed in some order.
+Implementations that do not support threads are not required to support
+the calling of these functions from threads.

 This section
 generally assumes a thread package similar to
Index: chap-inquiry/inquiry.tex
===================================================================
--- chap-inquiry/inquiry.tex	(revision 1970)
+++ chap-inquiry/inquiry.tex	(working copy)
@@ -55,6 +55,8 @@
 Valid (\const{MPI\_VERSION}, \const{MPI\_SUBVERSION}) pairs in
 this and previous versions of the \MPI/ standard
 are (3,0), (2,2), (2,1), (2,0), and (1,2).
+This function is callable from threads without restriction,
+see Section~\ref{sec:ei-threads}.

 \begin{funcdef}{MPI\_GET\_LIBRARY\_VERSION( version, resultlen )}
 \funcarg{\OUT}{version}{version string (string)}
@@ -1740,6 +1742,8 @@
 called does not affect the behavior of \mpifunc{MPI\_INITIALIZED}.
 It is one of the few routines that may be called before
 \mpifunc{MPI\_INIT} is called.
+This function is callable from threads without restriction,
+see Section~\ref{sec:ei-threads}.

 \begin{funcdef}{MPI\_ABORT(comm, errorcode)}
 \funcarg{\IN}{comm}{communicator of tasks to abort}
@@ -1848,6 +1852,8 @@
 This routine returns \mpiarg{true} if \mpifunc{MPI\_FINALIZE} has completed.
 It is valid to call \mpifunc{MPI\_FINALIZED}
 before \mpifunc{MPI\_INIT} and after \mpifunc{MPI\_FINALIZE}.
+This function is callable from threads without restriction,
+see Section~\ref{sec:ei-threads}.

 \begin{users}
 \mpi/ is ``active'' and it is thus safe to call \mpi/ functions if