KhronosGroup / KhronosGroup/OpenCL-Docs
overlap check in clEnqueueCopyBufferRect
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 421
- Forks
- 132
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
In clEnqueueCopyBufferRect, if src_buffer and dst_buffer are different sub-buffers of the same associated buffer object.
the src_row_pitch and dst_row_pitch do not need to be the same. But the "Checking for Memory Copy Overlap" only has one row_pitch, how do we input the row_pitch?
The slice_pitch has the same problem.
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 with the clEnqueueCopyBufferRect specification and its “Checking for Memory Copy Overlap” text. Compare how src_row_pitch, dst_row_pitch, src_slice_pitch, and dst_slice_pitch are defined for sub-buffers sharing an associated buffer. Done means the specification clearly explains which pitches are used when checking overlap.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100