KhronosGroup / KhronosGroup/OpenCL-CTS
Generic Address Space tests depend on Program Scope Global Variables support
- Dominant language
- C++
- Stars
- 232
- Forks
- 235
- Avg merge
- 8d 7h
- Merged PRs (30d)
- 18
Description
As of today it's not possible to run the Generic Address Space tests without supporting Program Scope Global Variables. Which means that implementations will pass those tests without them being run.
It doesn't look like it's a trivial change to port those tests away from using Program Scope Global Variables, so I'm wondering if we want to write entirely new tests or try to come up with an otherwise valid plan to solve this problem?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Generic Address Space tests and identifying where they require Program Scope Global Variables support. Review how those tests are executed and determine whether they can be ported or need new coverage. Done means Generic Address Space behavior is tested without requiring unsupported Program Scope Global Variables, with the chosen approach documented in the test suite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100