KhronosGroup / KhronosGroup/OpenCL-Docs
Clarify when returning CL_INVALID_IMAGE_SIZE is allowed
Open
Nobody has claimed this yet.
OpenCL API Spec
- Dominant language
- Python
- Stars
- 421
- Forks
- 132
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
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
Review the issue context and the linked OpenCL-CTS pull request #821 first to determine which OpenCL documentation and specification text need clarification. Done means the documentation clearly states when returning CL_INVALID_IMAGE_SIZE is allowed, with the relevant wording updated in the appropriate source.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100