KhronosGroup / KhronosGroup/OpenCL-Docs
What is the definition of a "valid event"
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
The phrase "...valid events" is used in every API that accepts an event waitlist, but there is no definition of what a valid event is.
I think a valid event is any event that can be queried by clGetEventInfo - returned by an OpenCL API, is associated with an active context (if applicable), and has not been destroyed (if applicable).
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 issue discussion and the OpenCL APIs that accept an event waitlist, especially clGetEventInfo. Done means the documentation records an agreed definition of a valid event and applies it consistently to those APIs.
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
- Mostly clear
- Newbie friendliness
- 30/100