Skip to content

Commit fda68a9

Browse files
committed
Fix Latex issue.
1 parent f6c03c5 commit fda68a9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/Infrastructure/VM/doc/VM_rest.tex

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@
1919

2020
\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}.
2121

22-
\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.
22+
\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.
2323

2424

2525
\end{enumerate}

0 commit comments

Comments
 (0)