From 6620f935028a61cc625096f7f8733a0187cfad19 Mon Sep 17 00:00:00 2001 From: Greg Lueck Date: Thu, 18 Jun 2026 14:19:12 -0400 Subject: [PATCH] Clarify "atomic_ref" with private address space Cherry pick #986 from main (cherry picked from commit b1fb5a4b70f096572cb551d8030b82e39cd5dfcf) --- adoc/chapters/programming_interface.adoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/adoc/chapters/programming_interface.adoc b/adoc/chapters/programming_interface.adoc index f118ca7ab..8add5020c 100644 --- a/adoc/chapters/programming_interface.adoc +++ b/adoc/chapters/programming_interface.adoc @@ -20496,6 +20496,11 @@ operations in device code with a syntax similar to the {cpp} standard [code]#std::atomic_ref#. The [code]#sycl::atomic_ref# class must not be used in host code. +The referenced object of type [code]#T# must not reside in the private address +space. +If [code]#atomic_ref# is constructed with a reference to an object in the +private address space, the behavior is undefined. + Unlike [code]#std::atomic_ref#, [code]#sycl::atomic_ref# does not provide a default memory ordering for its operations. Instead, the application must specify a default ordering via the