Skip to content

Commit

Permalink
Fix Latex issue.
Browse files Browse the repository at this point in the history
  • Loading branch information
theurich committed Aug 19, 2024
1 parent f6c03c5 commit fda68a9
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/Infrastructure/VM/doc/VM_rest.tex
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@

\item {\bf Data arrays in VM comm calls are {\em assumed shape} with rank=1.} Currently all dummy arrays in VM comm calls are defined as {\em assumed shape} arrays of rank=1. The motivation for this choice is that the use of assumed shape dummy arrays guards against the Fortran copy in/out problem. However it may not be as flexible as desired from the user perspective. Alternatively all dummy arrays could be defined as {\em assumed size} arrays, as it is done in most MPI implementations, allowing arrays of various rank to be passed into the comm methods. Arrays of higher rank can be passed into the current interfaces using Fortran array syntax. This approach is explained in section \ref{vm_higherrank}.

\item {\bf Limitations when using VMEpoch.} Using a blocking collective call (e.g. {\tt ESMF\_VMBroadcast()}, the {\tt MPI\_Bcast()} used by {\tt ESMF_InfoBroadcast()}, etc.) within the region enclosed by {\tt ESMF\_VMEpochEnter()} and {\tt ESMF\_VMEpochExit()} will result in a deadlock.
\item {\bf Limitations when using VMEpoch.} Using a blocking collective call (e.g. {\tt ESMF\_VMBroadcast()}, the {\tt MPI\_Bcast()} used by {\tt ESMF\_InfoBroadcast()}, etc.) within the region enclosed by {\tt ESMF\_VMEpochEnter()} and {\tt ESMF\_VMEpochExit()} will result in a deadlock.


\end{enumerate}
Expand Down

0 comments on commit fda68a9

Please sign in to comment.