KhronosGroup / KhronosGroup/OpenCL-Docs
Behaivor of failed events in nonblocking host side enqueues
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 421
- Forks
- 132
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
In clWaitForEvents CL_EXEC_STATUS_ERROR_FOR_EVENTS_IN_WAIT_LIST is returned for an event with a negative integer value. clEnqueueCopyBuffer does not have any language describing what happens if such an event appears in its wait list (the same applies to all non-blocking enqueue APIs - I think).
What is the expected behaviour for a failed event in a nonblocking enqueue's event wait list?
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 clWaitForEvents and clEnqueueCopyBuffer specifications, then compare the language for all non-blocking enqueue APIs. Done means the expected behavior for a failed event in an enqueue wait list is decided and documented consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100