From 7cc39e214ff24310da75a9d96247903caf3add1c Mon Sep 17 00:00:00 2001 From: GarveyJoe Date: Wed, 22 Dec 2021 11:27:06 -0500 Subject: [PATCH] Clarified device_global initialization ambiguity This is not meant to be a functional change to when initialization occurs; this was always out intent. I'm just trying to make the wording more clear. --- .../extensions/DeviceGlobal/SYCL_INTEL_device_global.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sycl/doc/extensions/DeviceGlobal/SYCL_INTEL_device_global.asciidoc b/sycl/doc/extensions/DeviceGlobal/SYCL_INTEL_device_global.asciidoc index 1b24659951fc0..e9827ea4794de 100755 --- a/sycl/doc/extensions/DeviceGlobal/SYCL_INTEL_device_global.asciidoc +++ b/sycl/doc/extensions/DeviceGlobal/SYCL_INTEL_device_global.asciidoc @@ -183,7 +183,7 @@ _T_ is restricted to types that have a trivial destructor and a trivial default Since _T_ is restricted to types with trivial default constructors in this version of the specification, there are no non-default `device_global` constructors, and therefore no initialization values may be specified for the content of a `device_global` allocation on a device. -The allocation of type _T_ is zero-initialized on each device prior to the first access to that `device_global` variable. +The allocation of type _T_ for a given `device_global` is zero-initialized on a given device prior to the first access to that `device_global` on that device. For the purposes of this definition an access can be a direct access of the `device_global` in kernel code or a copy to or from that `device_global` enqueued to the given device. Properties may be specified for a `device_global` to provide semantic modification or optimization hint information to the compiler. See the section