Undefined Behavior: Multiple initialization calls

[BryantLam]

@jdinan Please review:

openshmem-specification/content/backmatter.tex

Lines 178 to 181 in 551dca3

	Multiple calls to initialization routines & In an \openshmem program where
	the initialization routines \FUNC{shmem\_init} or \FUNC{shmem\_init\_thread}
	have already been called, any subsequent calls to these initialization routines
	result in undefined behavior.

[jdinan]

Looks fine, but I always wonder about the wisdom of this annex. We should not introduce new semantics in an annex, so this must be duplication, which is bad in a specification document. Then there's the problem of keeping this in sync. Do we intend for this to capture all scenarios that result in undefined behavior?

[BryantLam]

I hope not; there's a lot of them! I agree that I do not think this annex serves a purpose beyond reminding users of known gotchas that are already specified elsewhere. The same, however, could be said for 8.10.3 Synchronization and Communication Ordering in OpenSHMEM which gives examples for fence/quiet.

[BryantLam]

Maybe it would be more interesting to retool this annex as an index with backreferences to the routines.