Kévin Petit

Quite a few cases are indeed supported now. FWIW, all the `basic:vload*` conformance tests are now passing (with 8- and 16-element vectors disabled in the tests) but `basic:vstore_{local,private}` are still...

C++ for OpenCL itself is experimental and work-in-progress. The language documentation for C++ for OpenCL is maintained there: https://github.com/KhronosGroup/OpenCL-Docs/tree/master/cxx4opencl. Feedback on missing features of interest is welcome as issues in...

Ok, I'll do that. >Is there a usage model for the CL_API_SUFFIX__{EXPERIMENTAL,VERSION*} definitions or can they be removed? I actually started using them in https://github.com/KhronosGroup/OpenCL-Headers/pull/154 (which I'd like to get...

Even if we don't have a use for them at the moment I think I'd rather we keep the version-specific definitions as they enable to centrally manage this should we...

I agree extension function declarations will need some special care. The first idea that comes to mind is to use the minimum required version (which could at least be 1.0...

Linking https://github.com/KhronosGroup/OpenCL-Headers/issues/56

That's awesome! This would be a big enabler :). Regarding the missing `cl_khr_extended_versioning` definitions, I think it's mostly because we still haven't merged the spec PR (https://github.com/KhronosGroup/OpenCL-Docs/pull/218).

I don't feel too strongly about this. You're likely to be faster than me so if landing this quickly(ish) matters to you, it'd probably be better for you to work...

Thanks for this PR. I'll have a bit of a play before reviewing it. >also mention CLVK_MAX_CMD_{GROUP|BATCH}_SIZE in the readme Maybe you could extract that into a separate PR that...

>I think the trace macros introduced here could have a second backend using https://github.com/kpet/clvk/pull/281. Yup. We might even want to allow both at the same time.