KhronosGroup / KhronosGroup/OpenCL-Docs
OpenCL 3.0 lacking proper interoperability with newer graphics APIs
- Dominant language
- Python
- Stars
- 420
- Forks
- 131
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
Hopefully this is the right place to bring up these kinds of subjects.
The OpenCL spec contains extensions to support interoperability with old APIs such as DirectX11 and OpenGL. Yet, Nothing regarding Vulkan nor DirectX 12. APIs such as Cuda have these for ages.
Also, the specification of the existing APIs has not been updated for ages. for instance fine grain control over resource synchronization is lacking and some extensions are only available only with one API (such as mipmap support for OpenGL).
This interoperability is of enormous importance for any application dealing with compute AND visualization (computer vision). I can't understand why the Khronos group does not seem to touch on the subject in the new spec. Why is this then?
Contributor guide
Research direction
Review the OpenCL 3.0 interoperability sections and the existing DirectX 11 and OpenGL extensions in the specification sources; compare their coverage with the requested Vulkan and DirectX 12 interoperability. The issue does not name files or tests, and a concrete scope and maintainer decision are needed before completion can be defined.
Written by the indexing model from the issue text.
Assessment
- Domain
- computer-graphics, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100