Kévin Petit
Kévin Petit
Here are a few regressions I'm observing with this update: AMD/Intel/llvmpipe (logical and physical addressing) ``` Half Ops Expected the return code to be 0 but got 1 Expected the...
https://github.blog/2024-06-03-arm64-on-github-actions-powering-faster-more-efficient-build-systems/
The provisional specification for cl_khr_command_buffer defines a path to provide additional properties for NDRange kernel commands (clCommandNDRangeKernelKHR/cl_ndrange_kernel_command_properties_khr). This enables future extensibility which cl_khr_command_buffer_mutable_dispatch is already using. Do we want a...
- Add a khr+ext spec type to makeSpec and cover in CI - Document the version and dependencies of all EXT extensions in the XML - Integrate cl_ext_cxx_for_opencl into the...
Features are stored in a text file for now. Ultimately, we probably want to use the XML registry for this. Generation script taken from #1174 with a few modifications. Contributes...
On the 2020/08/04 teleconference, we decided that we'd resolve https://github.com/KhronosGroup/OpenCL-Docs/issues/317 by having `CL_*_PROPERTIES` queries return the values provided by the user as is. We also identified a special case that...
Prior to the unification of the OpenCL specifications, the specification for many extensions stated the version of OpenCL required by the extension. The new extension appendix no longer seems to...
The macros for OpenCL C features are currently defined manually in `c/feature-dictionary.asciidoc`. Here is an example: ``` // opencl_c_kernel_clock_scope_sub_group ifdef::backend-html5[] :opencl_c_kernel_clock_scope_sub_group: pass:q[`\__opencl_c_kernel_clock_scope_sub_group`] endif::[] ifndef::backend-html5[] :opencl_c_kernel_clock_scope_sub_group: pass:q[`\__opencl_c_​kernel_​clock_​scope_​sub_​group`] endif::[] ``` Authoring these...
Following the initial step towards a unified OpenCL specification that describes core features and extensions, a new appendix giving an overview of all the extensions included in the specification was...
The specification tooling now has some support for writing unified specification that comprise both core features and extensions. A next logical step seems to be to merge the SPIR-V environment...