KhronosGroup / KhronosGroup/OpenCL-Docs
Explicitly State Behavior when Host Pointer is freed after clCreateBuffer
- Dominant language
- Python
- Stars
- 420
- Forks
- 131
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
The specification does not state the behavior if `clCreateBuffer` is called with `CL_MEM_USE_HOST_PTR` and then the host pointer is freed in the memory flags, clCreateBuffer, or clCreateBufferWithProperties sections. Should it be added for explicitness and since the behavior would most likely be undefined?
Contributor guide
Research direction
Read the CL_MEM_USE_HOST_PTR memory-flags, clCreateBuffer, and clCreateBufferWithProperties sections named in the issue. Compare related pointer-lifetime wording elsewhere in the specification and confirm the intended behavior with maintainers. Done when the relevant sections explicitly describe what happens if the host pointer is freed.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100