KhronosGroup / KhronosGroup/OpenCL-CTS
Some image array test cases does not work properly for embedded profile.
- Dominant language
- C++
- Stars
- 232
- Forks
- 235
- Avg merge
- 8d 7h
- Merged PRs (30d)
- 18
Description
https://github.com/KhronosGroup/OpenCL-CTS/blob/6a64c5a0c74b9e4a83025628f2cdb746647cdfb1/test_conformance/api/test_mem_object_info.cpp#L532
https://github.com/KhronosGroup/OpenCL-CTS/blob/6a64c5a0c74b9e4a83025628f2cdb746647cdfb1/test_conformance/images/samplerlessReads/test_read_1D_array.cpp#L253
https://github.com/KhronosGroup/OpenCL-CTS/blob/6a64c5a0c74b9e4a83025628f2cdb746647cdfb1/test_conformance/images/samplerlessReads/test_read_2D_array.cpp#L245
According to the OpenCL Specification 1.2, the minimum value of CL_DEVICE_IMAGE_MAX_ARRAY_SIZE can be 256 for Ebedded Profile.
The code above cannot work properly when the Max Array Size is 256.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the referenced code in test_conformance/api/test_mem_object_info.cpp and the samplerless image tests test_read_1D_array.cpp and test_read_2D_array.cpp. Compare the array-size assumptions at the cited lines with the OpenCL 1.2 embedded-profile minimum of 256. Done means the affected cases work correctly when CL_DEVICE_IMAGE_MAX_ARRAY_SIZE is 256.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100