Make pyopencl fit for OpenCL 3.1
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 247
- Avg merge
- 7h 2m
- Merged PRs (30d)
- 6
Description
The Khronos Group has [announced](https://www.khronos.org/blog/opencl-3.1-is-here) the release of [OpenCL 3.1](https://registry.khronos.org/OpenCL/specs/unified/html/OpenCL_API.html). This ticket is intended to serve as a collector for others for all necessary overhauls (behavioural changes, optimizations as well as source code refactoring) originating from this, if there are any.
Changes within the spec are collected [here](https://registry.khronos.org/OpenCL/specs/unified/html/OpenCL_API.html#_summary_of_changes_from_opencl_3_0_to_opencl_3_1).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the OpenCL 3.1 specification and its summary of changes from OpenCL 3.0, linked in the issue. Audit pyopencl for the necessary behavioral changes, optimizations, and source refactoring; done means identifying and addressing all applicable changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- hpc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100