On 5/30/25 16:36, Tobias Burnus wrote:
Attached patch adds omp_target_memset and omp_target_memset_async
permitting to set (potentially large) data on the device to a
certain value - in particular to '\0'.
It uses 'memset' on the host (and for shared memory, e.g. via
requires unified_shared_memory/self_maps). For nvptx, cuMemsetD8
is used and for AMD GPUs hsa_amd_memory_fill. However, the latter
only supports 4byte aligned data, working in multiples of 4byte.
@Sandra: Any .texi comments? (Or generic comments.)
I have only one nit about the documentation part: in both instances of
+The @var{device_num} must be conforming device number and @var{ptr} must be
please s/conforming/a conforming/
-Sandra
