KhronosGroup / KhronosGroup/OpenCL-Docs
Clarifying spec consistency around order of results related to CL_CONTEXT_DEVICES query and possibly few more
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 421
- Forks
- 132
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
During review of CTS PR 2177 it was noted by @bashbaug that the result of the CL_CONTEXT_DEVICES query is not required by the specification to retain the same order as was used during the context creation. This inconsistency may be unexpected for users who likely assume the order will remain consistent.
Similar problem may refer to two more queries:
CL_COMMAND_BUFFER_QUEUES_KHRCL_COMMAND_BUFFER_PROPERTIES_ARRAY_KHR
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 OpenCL specification text for the CL_CONTEXT_DEVICES query and compare its ordering language with the context-creation requirements. Then inspect the corresponding wording for CL_COMMAND_BUFFER_QUEUES_KHR and CL_COMMAND_BUFFER_PROPERTIES_ARRAY_KHR; done means the specification is consistent about whether each query preserves creation order.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100