Merge branch 'main' into error-code-consistency

Author: bashbaug

.github/workflows/release.yml

@@ -46,7 +46,7 @@ jobs:
             python3 makeSpec -clean -spec khr+ext OUTDIR=out.release -j 5 api c env ext cxx4opencl
 
       - name: Release Specs
-        uses: softprops/action-gh-release@6cbd405e2c4e67a21c47fa9e383d020e4e28b836 # v2.3.3
+        uses: softprops/action-gh-release@6da8fa9354ddfdc4aeace5fc48d7f679b5214090 # v2.4.1
         with:
             draft: true
             files: |

api/opencl_architecture.asciidoc

@@ -578,12 +578,12 @@ Consider the following three domains of synchronization in OpenCL:
     for execution
 
 
-Synchronization across all work-items within a single work-group is carried
-out using a _work-group function_.
-These functions carry out collective operations across all the work-items in
-a work-group.
-Available collective operations are: barrier, reduction, broadcast, prefix
-sum, and evaluation of a predicate.
+Synchronization across work-items within a work-group is done by using a
+_work-group function_.
+These functions perform collective operations across the work-items in a
+work-group.
+Available collective operations include barriers, reductions, broadcast, prefix
+sums, and evaluation of a predicate.
 A work-group function must occur within a converged control flow; i.e. all
 work-items in the work-group must encounter precisely the same work-group
 function.
@@ -592,27 +592,18 @@ must encounter the same work-group function in the same loop iterations.
 All the work-items of a work-group must execute the work-group function and
 complete reads and writes to memory before any are allowed to continue
 execution beyond the work-group function.
-Work-group functions that apply between work-groups are not provided in
+Work-group functions that apply across work-groups are not provided in
 OpenCL since OpenCL does not define forward-progress or ordering relations
 between work-groups, hence collective synchronization operations are not
 well defined.
 
-Synchronization across all work-items within a single sub-group is carried
-out using a _sub-group function_.
-These functions carry out collective operations across all the work-items in
-a sub-group.
-Available collective operations are: barrier, reduction, broadcast, prefix
-sum, and evaluation of a predicate.
-A sub-group function must occur within a converged control flow; i.e. all
-work-items in the sub-group must encounter precisely the same sub-group
-function.
-For example, if a work-group function occurs within a loop, the work-items
-must encounter the same sub-group function in the same loop iterations.
-All the work-items of a sub-group must execute the sub-group function and
-complete reads and writes to memory before any are allowed to continue
-execution beyond the sub-group function.
-Synchronization between sub-groups must either be performed using work-group
-functions, or through memory operations.
+Synchronization across work-items within a sub-group is done by using a
+_sub-group function_.
+These functions perform collective operations across the work-items in a
+sub-group.
+Like work-group functions, sub-group functions must also occur within a
+converged control flow; i.e. all work-items in the sub-group must encounter
+precisely the same sub-group function.
 Using memory operations for sub-group synchronization should be used
 carefully as forward progress of sub-groups relative to each other is only
 supported optionally by OpenCL implementations.

api/opencl_platform_layer.asciidoc

@@ -367,7 +367,7 @@ errors footnote:[{fn-error-precedence}].
     ** if _platform_ is not a valid platform
   * {CL_INVALID_VALUE}
     ** if _param_name_ is not one of the supported values
-    ** if the size in bytes specified by _param_value_size_ is less than size of
+    ** if the size in bytes specified by _param_value_size_ is less than the size of
     the return type specified in the <<platform-queries-table, Platform
     Queries>> table and _param_value_ is not `NULL`
   * {CL_OUT_OF_HOST_MEMORY}
@@ -2274,7 +2274,7 @@ Otherwise, it returns one of the following errors:
     ** if _device_ is not a valid device
   * {CL_INVALID_VALUE}
     ** if _param_name_ is not one of the supported values
-    ** if the size in bytes specified by _param_value_size_ is less than size of
+    ** if the size in bytes specified by _param_value_size_ is less than the size of
     the return type specified in the <<device-queries-table, Device Queries>>
     table and _param_value_ is not `NULL`
   * {CL_OUT_OF_RESOURCES}
@@ -3776,7 +3776,7 @@ Otherwise, it returns one of the following errors:
     ** if _context_ is not a valid context
   * {CL_INVALID_VALUE}
     ** if _param_name_ is not one of the supported values
-    ** if the size in bytes specified by _param_value_size_ is less than size of
+    ** if the size in bytes specified by _param_value_size_ is less than the size of
     the return type specified in the <<context-info-table, Context Queries>>
     table and _param_value_ is not `NULL`
   * {CL_OUT_OF_RESOURCES}