KhronosGroup / KhronosGroup/OpenCL-Docs
Clarification on zero sizes in clEnqueueXXXBuffer APIs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 421
- Forks
- 132
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
This might be a simple question to answer as it's arguably the status quo in the specification, but because it has caused a discussion internally I'd like to ask for clarification about whether the clEnqueue(Read|Write|Copy|Fill)Buffer functions allow a size parameter of 0.
As far as I can determine, the specification doesn't say it is an error so it's presumably not an error. I can't see any test in the OpenCL-CTS testing that it's an acceptable (or unacceptable) value, though. Should it? If so, I can take this issue over there.
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 reviewing the specification text for the clEnqueue(Read|Write|Copy|Fill)Buffer APIs and the OpenCL-CTS coverage mentioned in the issue. Done means resolving whether size=0 is permitted and documenting that clarification or directing a follow-up CTS test.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100