You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The MPI standard currently does not explicitly state whether or not it guarantees variable availability once MPI_T is finalized and potentially re-initialized again. The scope of the guarantees given needs to be clarified.
The text was updated successfully, but these errors were encountered:
As discussed in the last meeting, I added text to define "MPI tool epochs" and referenced them at the places where variable scope is discussed. Corresponding text passages are highlighted in the attached file. mpi32-report_issue_33.pdf
We discussed this in the Chicago Feb 2016 MPI Forum meeting, during the tools WG.
The consensus was that we don't need to add any text to address this. The value of a variable can change at any time -- even 2 consecutive calls to cvar_read could return different values if someone else wrote a new value.
So: no guarantees are given about the read values. No text to add here.
The MPI standard currently does not explicitly state whether or not it guarantees variable availability once MPI_T is finalized and potentially re-initialized again. The scope of the guarantees given needs to be clarified.
The text was updated successfully, but these errors were encountered: