From 29da90ceca5a478154daa0476aba68dda838bbc6 Mon Sep 17 00:00:00 2001 From: Greg Lueck Date: Sun, 25 Aug 2024 10:52:38 -0400 Subject: [PATCH] Fix spelling --- adoc/chapters/programming_interface.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/adoc/chapters/programming_interface.adoc b/adoc/chapters/programming_interface.adoc index a3237101..00de4da3 100644 --- a/adoc/chapters/programming_interface.adoc +++ b/adoc/chapters/programming_interface.adoc @@ -412,7 +412,7 @@ a@ required for the underlying <> specified in the <> specification document, if this SYCL [code]#T# instance was originally constructed using one of the backend interoperability - [code]#make_*# functions specified in + [code]#make_*# functions specified in <>. See the relevant backend specification for details. @@ -10207,7 +10207,7 @@ modification of shared allocations through the aspect See <> in <> for more details. Performance hints for shared allocations may be specified by the user by -enqueueing [code]#prefetch# operations on a device. +enqueuing [code]#prefetch# operations on a device. These operations inform the SYCL runtime that the specified shared allocation is likely to be accessed on the device in the future, and that it is free to migrate the allocation to the device. @@ -16478,7 +16478,7 @@ executions are decoupled from one another except at specific points. For example, device code executions often begin when dependencies in the SYCL task graph are satisfied, which occurs asynchronously from host code execution. As a result of this the errors that occur on a device cannot be thrown directly -from a host API call, because the call enqueueing a device action has typically +from a host API call, because the call enqueuing a device action has typically already returned by the time that the error occurs. Such errors are not detected until the error-causing task executes or tries to execute, and we refer to these as <>.