[mpiwg-tools] MPI_T question about cvar value guarantees

[Jeff Squyres (jsquyres)]

> On Feb 5, 2016, at 4:26 PM, Schulz, Martin <schulz6 at llnl.gov> wrote:
> 
> That¹s a good question and I don¹t think we say - my original intent when
> writing the document (based on my personal model that I had in my head for
> this) was to provide no guarantees once MPI_T gets uninitialized, so in
> this case both versions would be OK. In fact, it could be even worse -
> what happens in case 1 if the component is not reloaded? Do you still have
> access to the variable at all? This is probably more likely if the MPI_T
> only block is after MPI_Finalize (since this would unload components), but
> the principle is the same.
> 
> For the discovery/query routines we state that the numbering is not
> allowed to change between ³runs², which may have been the wrong thing to
> say - it probably should say ³while MPI_T is initialized². In this case,
> there would really not be any guarantees at all. If you wanted guarantees,
> you would have to keep MPI_T initialized.

That sounds fine to me.  I think that this is worth an errata.

-- 
Jeff Squyres
jsquyres at cisco.com
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/