Updating Annex C Undefined Behavior in OpenSHMEM

[ahayashi]

Problem Statement

The v1.6 spec clarifies the behavior of shmem_team_split_stride when 1) the stride argument is 0 or negative, and 2) the input arguments imply a wrap-around with respect to the parent teams's PEs:

• content/shmem_team_split_strided.tex (L60)

If a $stride$ value equal to 0 is passed to \FUNC{shmem\_team\_split\_strided},
then the $size$ argument passed must be 1, or the behavior is undefined.
If the triplet provided to \FUNC{shmem\_team\_split\_strided} implies a
wrap-around sequence, the input is considered invalid and the behavior is
undefined.

Proposed Changes

If this makes sense and it's not too late, we'd suggest adding "Undefined Behavior in OpenSHMEM" to Annex C.

Credit: @youssefelmougy

Impact on Implementations

N/A

Impact on Users

N/A

References and Pull Requests

#554

[davidozog]

See #557