Kévin Petit

Only properties defined using `CL_QUEUE_PROPERTIES` are currently supported. Arbitrary queue properties such as the ones added by vendor extensions aren't supported.

We support a lot of configuration options (probably too many), compilers, OpenCL versions etc with these bindings; definitely too many to test all combinations exhaustively. The testing we have currently...

When building with `CL_HPP_ENABLE_EXCEPTIONS` enabled, exceptions are thrown when OpenCL calls fail. The string returned by the `what()` method of the exceptions tends to only contain the entrypoint name. Adding...

Code sample to use OpenCL on Android

1

The following cases would be interesting to cover: - In a native binary - As part of an APK

Utility function to map error codes to a string

2

Many projects are rolling their own and most of them end up with missing error codes over time. Should we provide an official solution? An example of the many such...

No implementers (and no interest expressed), no CTS tests. These extensions should not be part of the specification. Change-Id: I064076c8075b5947ef9109558c4b03da426e4505

The current specification makes it impossible to support a fully read-only image format (and related `cl_mem_flags` issues)

4

As part of adding support for a new image format for which we can only support read access, we're bumping into the following rule (there are similar notes for **clEnqueueFillBuffer**,...

Some design elements of the OpenCL API are central to the API philosophy and likely ought to be documented as such in the OpenCL specification. Here are a few examples...

The AtomicFloat16AddEXT capability it defines is referred to. Change-Id: Icbae5f1ad02561e11517a47e9640eea4bc6a4283