KhronosGroup / KhronosGroup/OpenCL-Docs
Does the dispatch_data field set by clIcdSetPlatformDispatchDataKHR need to be read atomically?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 421
- Forks
- 132
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
I can see a situation where thread 1 calls clIcdSetPlatformDispatchDataKHR to update the dispatch_data field of the cl_platform_id object, then thread 2 relies on the value to be visible in a future API call. Are ICD loaders required to fetch the dispatch_data field atomically? Does this need to be specified? Are there other ways to guarantee that the value is indeed visible to the ICD loader in other threads?
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 clIcdSetPlatformDispatchDataKHR entry point and the dispatch_data visibility question raised in the issue. A completed change would clarify whether ICD loaders must read the field atomically and specify how visibility across threads is guaranteed.
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