KhronosGroup / KhronosGroup/OpenCL-CTS
Unused variables in images/kernel_read_write
- Dominant language
- C++
- Stars
- 232
- Forks
- 235
- Avg merge
- 8d 7h
- Merged PRs (30d)
- 18
Description
There are many unused variables in images/kernel_read_write and it is not clear whether these are truly unneeded or whether they reveal a hole in the testing logic.
For example most test_read_*.cpp files contain `float maxErr = get_max_relative_error(...)` which is later hardcoded to `0.5`.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the files under images/kernel_read_write, especially the test_read_*.cpp files, and trace how values such as maxErr from get_max_relative_error are used. Determine whether each unused variable reflects dead code or a testing gap; done means the variables and tests consistently represent the intended checks, with the relevant test suite passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100