Ben Ashbaugh
Ben Ashbaugh
The [query](https://registry.khronos.org/OpenCL/specs/3.0-unified/html/OpenCL_API.html#_semaphore_queries) for `clGetSemaphoreInfoKHR(CL_SEMAPHORE_DEVICE_HANDLE_LIST_KHR)` says: > Returns the list of OpenCL devices the semaphore is associated with. But, the spec is ambiguous how to "associate" a device with a semaphore,...
fixes #1152 fixes #1244 Rephrases and corrects the descriptions for multiple parts of clSetKernelExecInfo. Removes the cumbersome "note" below the API description and moves the content into the API description...
Fixes #1114 Rephrases and simplifies the requirements to properly use and modify shared OpenCL objects. Refers to the chapter describing the OpenCL memory consistency model vs. duplicating information.
The spec currently says: > num_mip_levels must be 0 unless the [cl_khr_mipmap_image](https://registry.khronos.org/OpenCL/specs/3.0-unified/html/OpenCL_API.html#cl_khr_mipmap_image) extension is supported, in which case it must be a value greater than 1 specifying the number of...
This fixes most of #1216. * Improves the spec consistency for all of the _param_value_size_ argument descriptions. * Improves the spec consistency for all of the error conditions related to...
In the current SPIR-V environment spec, we describe the "data format for reading and writing images": https://registry.khronos.org/OpenCL/specs/3.0-unified/html/OpenCL_Env.html#_data_format_for_reading_and_writing_images Most image channel orders return four components for reading or accept four components...
Found while working on the fix for #1152. The description for [`CL_KERNEL_EXEC_INFO_SVM_FINE_GRAIN_SYSTEM`](https://github.com/KhronosGroup/OpenCL-Docs/issues/new#CL_KERNEL_EXEC_INFO_SVM_FINE_GRAIN_SYSTEM) is currently (**emphasis** mine): > This flag indicates whether the kernel uses pointers that are fine grain system...
Fixes #841 Documents the valid coordinate types when reading from or writing to images. This should match what is supported by OpenCL C and what is generated by Clang and...
The OpenCL C and SPIR-V environment specs are missing descriptions in many places regarding the `CL_UNORM_SHORT_565` and `CL_UNORM_SHORT_555` image channel orders. For example: * OpenCL C Section 8.3 Conversion Rules...
This description is confusing and should be cleaned up: https://registry.khronos.org/OpenCL/specs/3.0-unified/html/OpenCL_C.html#cl_khr_fp16 > The cl_khr_fp16 extension was promoted to OpenCL C 1.2 as an optional feature, and to OpenCL 3.0 as the...