Ben Ashbaugh

Another: * `implementation defined` or `implementation-defined`

I found one more: `kernel instance` vs. `kernel-instance`.

It may be wise to separate any issues specific to `cl_khr_expect_assume` from a general policy/philosophy. I'd forgotten about the various issues we encountered with `cl_khr_expect_assume`, but for Khronos folks they're...

> But I agree, introducing some sort of error for when this limit is exceeded makes sense... Serious question, do we really expect we may overflow sync points anytime in...

> Then again I don't think anything is preventing implementations from reserving some of those bits to represent arbitrary internal data so long as each sync point remains unique? Interesting...

A query for a device maximum seems a little artificial since (on some implementations at least) the maximum will be limited by available resources in the system and not some...

This sounds reasonable to me - I think I hinted at something similar here https://github.com/KhronosGroup/OpenCL-Docs/issues/19#issuecomment-436463265. > Backwards compatibility: Old code will continue to compile. Is there also a risk that...

I added a few more examples to the google doc spreadsheet linked above. So far, it looks like we will need an extension pragma for maximum portability with existing Clang-based...

I see now that my list in the [comment above](https://github.com/KhronosGroup/OpenCL-Docs/issues/82#issuecomment-785496025) is the same list as @AnastasiaStulova's [comment earlier in this issue](https://github.com/KhronosGroup/OpenCL-Docs/issues/82#issuecomment-635467096) - that seems like a good thing. We discussed...

Related CTS issue: https://github.com/KhronosGroup/OpenCL-CTS/issues/886