KhronosGroup / KhronosGroup/OpenCL-Docs
minimum value for CL_DEVICE_MAX_WRITE_IMAGE_ARGS for OpenCL 3.x device
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 421
- Forks
- 132
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
What should the minimum value be for CL_DEVICE_MAX_WRITE_IMAGE_ARGS for an OpenCL 3.x device?
From CTS discussion:
Also fixed the minimum for
CL_DEVICE_MAX_WRITE_IMAGE_ARGS, which per tables 63 and 64 in the 3.1.1 spec is 64 for the full profile and 8 for embedded. The test was checking against 8 and 1.
I think we should make this change in a separate PR, since it looks like a number of currently conformant implementations are returning a value smaller than 64 today, see the gpuinfo.org database.
Note that the minimum value was 8 for an OpenCL 1.2 implementation, then 64 for an OpenCL 2.x implementation, which was carried forward for OpenCL 3.x implementations.
Originally posted by @bashbaug in https://github.com/KhronosGroup/OpenCL-CTS/pull/2632#discussion_r3896724273
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the OpenCL 3.1.1 specification tables 63 and 64 and the current CL_DEVICE_MAX_WRITE_IMAGE_ARGS definition in the OpenCL-Docs sources. Verify the full-profile minimum is 64 and the embedded-profile minimum is 8, then update the relevant documentation and check for any related consistency checks.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100