RMA WG 09 13 2018

Agenda

(Naveen) )Addition of restrict qualifier in shmem_put_signal – reason other than user understandability?
(Nick) Can src and dest point to the same address? Should user be allowed or receive any warning/error for using such?
(Jim) Confirmed warning from gcc when the same pointer is used for two different arguments; does not depend on the function body. No warnings from clang.
(Naveen) Will do some more experimentation on this and report on the issue; it’s not safe to use restrict for both signal and dest buffer in shmem_put_signal
(Min) May not be safe to use restrict based on the definition provided
(Naveen) P2p synchronization introduction has added text for put with signal for maintaining memory ordering
(Jim) Revisit the issue of overlapping arrays in the spec (reduction)
(Naveen) Non-blocking AMO APIs, 8 new APIs proposed. Issue 246
(Nick) Does the return variable need to be symmetric? Any ordering guaranteed?
(Jim) Should we differ until figuring out how shmem_wait works for local?
(Naveen) API name too long for compare swap?
(Jim) New text for ctx APIs has been added. Need to update accordingly.
(Naveen) No example is provided for NB AMO yet.
(Jim) Can provide a bucket exchange algorithm with NB FADD. Can show one usage pattern.
(Naveen) PR is open for NB AMO. Suggestions are welcome.