CTS should verify device limits for FULL_PROFILE and EMBEDDED_PROFILE devices

Open
#2,555 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
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
testing-qa

Research direction

Start by locating the CTS checks for device image argument limits and compare their coverage with the FULL_PROFILE and EMBEDDED_PROFILE requirements stated in the issue. Review similar device-limit tests and determine whether the expected values should be relaxed or more cases added. Done means the chosen policy is covered by tests for both profiles and the relevant device-limit checks pass.

Written by the indexing model from the issue text.

Description

I just noticed today that e.g. Nvidia is reporting 32 write image args on a FULL_PROFILE device, but the specification states:

Max number of image objects arguments of a kernel declared with the write_only qualifier. The minimum value is 64 if CL_DEVICE_IMAGE_SUPPORT is CL_TRUE, the value is 0 otherwise.

The embedded profile requires at least 8 here.

What should we do about that? Relax the limit, because to be frank 64 is quite high or add more tests and just verify it?

I'm sure there are other issues like this around.

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.