KhronosGroup / KhronosGroup/OpenCL-Docs
determine the proper value for CL_TERMINATED_KHR
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 421
- Forks
- 132
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
See: https://github.com/KhronosGroup/OpenCL-Docs/issues/813#issuecomment-1237515848
The extension spec for cl_khr_terminate_context describes the event state CL_TERMINATED_KHR for events when a context is terminated but this event state is not included in the headers or XML file for this extension. We need to decide what this event state should be, and in particular, whether it should be a positive value or a negative (error) value.
There are some hints in internal bugzilla 8807 that it was intended to be a negative value.
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 cl_khr_terminate_context extension specification and compare its CL_TERMINATED_KHR event state against the extension headers and XML file. Review the linked OpenCL-Docs discussion and the cited internal bugzilla hint, then document the resolved value and update the affected specification sources and generated definitions.
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