KhronosGroup / KhronosGroup/OpenCL-Docs
Behaviour of CL_*_PROPERTIES queries with pointer values
Open
@kpet is already working on this.
Since Sep 8, 2020.
- Dominant language
- Python
- Stars
- 421
- Forks
- 131
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
On the 2020/08/04 teleconference, we decided that we'd resolve https://github.com/KhronosGroup/OpenCL-Docs/issues/317 by having CL_*_PROPERTIES queries return the values provided by the user as is. We also identified a special case that warranted further discussion: that of pointer property values. Specifically:
- Are applications required to keep the memory pointed to by pointer values accessible for the lifetime of objects created with a pointer value passed as property? This does not seem desirable.
- Should implementations return the pointer value that was passed knowing that it may no longer point to valid memory at the time where it is returned?
- Should implementations make a copy of the memory referenced by pointer property values and replace it with the pointer to the copy they maintain when properties are queried?
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.
Assessment
This issue has not been assessed yet.