KhronosGroup / KhronosGroup/OpenCL-SDK
Pipe Constructor fails
- Dominant language
- C++
- Stars
- 777
- Forks
- 163
- Avg merge
- 6d 17h
- Merged PRs (30d)
- 2
Description
In the cl::pipe constructor, "flags = CL_MEM_READ_WRITE | CL_MEM_HOST_NO_ACCESS;" results in error -30. Changing it to merely "CL_MEM_READ_WRITE" causes it to work fine. I saw this was an open issue in another, I think more outdated, repo. Actually, in that issue, someone suggested that =201 works. I do not understand the source of 201 as it does not fit the enumeration.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the cl::pipe constructor and inspect how its flags are passed to the OpenCL pipe creation call. Reproduce the error -30 with CL_MEM_HOST_NO_ACCESS, then consult the relevant OpenCL specification and existing tests or examples. Done means the constructor uses valid flags and the pipe can be created without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- hpc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100