KhronosGroup / KhronosGroup/OpenCL-Docs
clGetKernelArgInfo - behavior when program created with clCreateProgramWithIL
- Dominant language
- Python
- Stars
- 420
- Forks
- 131
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
Currently, the spec for [clGetKernelArgInfo](https://registry.khronos.org/OpenCL/specs/unified/html/OpenCL_API.html#clGetKernelArgInfo) says:
> Kernel argument information is only available if the program object associated with kernel:
> is created with [clCreateProgramWithBinary](https://registry.khronos.org/OpenCL/specs/unified/html/OpenCL_API.html#clCreateProgramWithBinary) and the program executable is built with the -cl-kernel-arg-info and -x spir options specified in the options argument to [clBuildProgram](https://registry.khronos.org/OpenCL/specs/unified/html/OpenCL_API.html#clBuildProgram) or [clCompileProgram](https://registry.khronos.org/OpenCL/specs/unified/html/OpenCL_API.html#clCompileProgram), if the [cl_khr_spir](https://registry.khronos.org/OpenCL/specs/unified/html/OpenCL_API.html#cl_khr_spir) extension is supported; or,
> is created with [clCreateProgramWithSource](https://registry.khronos.org/OpenCL/specs/unified/html/OpenCL_API.html#clCreateProgramWithSource) and the program executable is built with the -cl-kernel-arg-info option specified in the options argument to [clBuildProgram](https://registry.khronos.org/OpenCL/specs/unified/html/OpenCL_API.html#clBuildProgram) or [clCompileProgram](https://registry.khronos.org/OpenCL/specs/unified/html/OpenCL_API.html#clCompileProgram),
This does not cover the case in which the program has been created with clCreateProgramWithIL. What should be the behavior in this case?
Once this is decided, the appropriate change should be applied to the pipes test (https://github.com/KhronosGroup/OpenCL-CTS/blob/main/test_conformance/pipes/test_pipe_info.cpp)
Contributor guide
Research direction
Start by reviewing the clGetKernelArgInfo specification text and the clCreateProgramWithIL case described in the issue. Then inspect test_conformance/pipes/test_pipe_info.cpp. Done means the behavior is resolved and the relevant specification and pipes test are updated consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, testing
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100