Improve get_global_id() usage and coverage in OpenCL CTS

Open
#2,549 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
testing-qa

Research direction

Start by auditing the OpenCL CTS code paths that use get_global_id() and related functions, checking how their results are stored. Add coverage for values exceeding the 32-bit range and verify that results are handled as size_t; done means the identified usage issues are corrected and the new coverage passes.

Written by the indexing model from the issue text.

Description

A couple of issues wrt current usage and coverage of get_global_id() and related functions -

  • Most of the CTS code use int to store results of get_global_id that returns size_t
  • CTS doesn't seem to have coverage for large values exceeding 32-bit range.
Dominant language
C++
Stars
234
Forks
240
Avg merge
6d 12h
Merged PRs (30d)
15

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from KhronosGroup/OpenCL-CTS

All issues in KhronosGroup/OpenCL-CTS

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.