KhronosGroup / KhronosGroup/OpenCL-CTS
Supporting OpenCL 1.1
- Dominant language
- C++
- Stars
- 232
- Forks
- 235
- Avg merge
- 8d 7h
- Merged PRs (30d)
- 18
Description
Overall the CTS usually assumes that at least OpenCL 1.2 is being used/tested. The main changes are to add missing `Version(1, 2)` to tests validating 1.2 features, and using/enabling corresponding extensions prior to them having been merged into core (like cl_khr_fp64, for example).
(Initial list of) tests to update:
* [ ] api
* [ ] Allow OpenCL 1.1 devices (api_min_max,queries);
* [ ] Add `Version(1, 2)`.
* [ ] basic
* [ ] Enable cl_khr_fp64.
* [ ] buffers
* [ ] Add `Version(1, 2)`.
* [ ] device_partition
* [ ] Add `Version(1, 2)`.
* [ ] events
* [ ] Add `Version(1, 2)`.
* [ ] images
* [ ] Add `Version(1, 2)`.
* [ ] mem_host_flags
* [ ] Add `Version(1, 2)`.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the listed CTS areas: api, basic, buffers, device_partition, events, images, and mem_host_flags. Compare their existing version checks and extension handling, then update the OpenCL 1.2 assumptions so OpenCL 1.1 devices are supported where specified. Done means the checklist is covered and the affected conformance tests pass for OpenCL 1.1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100