KhronosGroup / KhronosGroup/OpenCL-CTS
CTS should verify device limits for FULL_PROFILE and EMBEDDED_PROFILE devices
- Dominant language
- C++
- Stars
- 232
- Forks
- 235
- Avg merge
- 8d 7h
- Merged PRs (30d)
- 18
Description
I just noticed today that e.g. Nvidia is reporting 32 write image args on a FULL_PROFILE device, but the specification states:
> Max number of image objects arguments of a kernel declared with the write_only qualifier. The minimum value is 64 if [CL_DEVICE_IMAGE_SUPPORT](https://registry.khronos.org/OpenCL/specs/3.0-unified/html/OpenCL_API.html#CL_DEVICE_IMAGE_SUPPORT) is [CL_TRUE](https://registry.khronos.org/OpenCL/specs/3.0-unified/html/OpenCL_API.html#CL_TRUE), the value is 0 otherwise.
The embedded profile requires at least 8 here.
What should we do about that? Relax the limit, because to be frank 64 is quite high or add more tests and just verify it?
I'm sure there are other issues like this around.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the CTS checks for device image argument limits and compare their coverage with the FULL_PROFILE and EMBEDDED_PROFILE requirements stated in the issue. Review similar device-limit tests and determine whether the expected values should be relaxed or more cases added. Done means the chosen policy is covered by tests for both profiles and the relevant device-limit checks pass.
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
- Needs clarification
- Newbie friendliness
- 35/100