Ben Ashbaugh

I think this is a good long-term goal, but it might be a good idea to keep the standalone extension spec around for one more release, to give time for...

Can you say a bit more how you expect these changes to be used? As-written they will require some updates to some of the tooling based on the XML file...

> In particular, the test fails now, but it seems to have nothing to do with my changes. Maybe some of the recently merged PRs conflict with each other? I...

> Does it maybe make sense to create an issue like how you did for #798 to facilitate discussion? Yes, I think this would be helpful, +1. As for moving...

Hello, here are a few suggestions to break this PR up further. I don't think you necessarily need to do all of these, but I think a few of the...

Thanks for separating out the changes and explaining the rationale for (1), (2), and (3)! Let's leave this more-or-less as-is for now, since it's already a pretty lengthy PR. Once...

Discussed in the April 16th teleconference. - The text in question is from an Appendix and is largely unchanged from the OpenCL 1.0 specification. We suspect that it should have...

The appendix is basically describing three scenarios / requirements, and I believe all of them are already covered by the memory model, in the [Host-Side and Device-Side Commands](https://registry.khronos.org/OpenCL/specs/3.0-unified/html/OpenCL_API.html#_host_side_and_device_side_commands) section: 1....

Observed in the April 16th teleconference: there is additional confusion here: https://registry.khronos.org/OpenCL/specs/3.0-unified/html/OpenCL_C.html#double-precision-support * There is a trailing comma. * Need to clarify that fp64 is only supported on OpenCL 1.2...

Proposal: * Acquiring or Releasing an external memory object must be performed by a command queue associated with a device in the device handle list associated with the memory object(s)....