SPIR-V 1.6 Testing
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- cpp
- Domain
- compilers, testing-qa
Research direction
Start by reviewing the unchecked SPIR-V 1.6 behaviors in this issue and the linked OpenCL-CTS pull requests for related test patterns. Done means covering FP Fast Math Mode cases, DotProduct availability, and bogus non-semantic extended instruction sets, while accounting for the listed restrictions.
Written by the indexing model from the issue text.
Description
Here is one more issue to track SPIR-V 1.6 testing.
-
New Behavior:
- Adds a new Nontemporal image operand. https://github.com/KhronosGroup/OpenCL-CTS/pull/2249
- The FP Fast Math Mode can apply to many more instructions:
- OpFNegate
- Comparison instructions such as OpOrdered, OpUnordered, OpFOrdEqual, etc.
- Extended instructions - TBD, which ones?
- Adds the UniformDecoration capability, and Uniform and UniformId decorations. https://github.com/KhronosGroup/OpenCL-CTS/pull/2254
- DotProduct and associated instructions may now be available without SPV_KHR_integer_dot_product. https://github.com/KhronosGroup/OpenCL-CTS/pull/2258
- "NonSemantic" extended instruction sets are available.
- Test that bogus non-semantic extended instruction sets are accepted, and that instructions from this non-semantic extended instruction set are ignored.
- Note: For other, known non-semantic extended instruction sets, additional testing will be done as part of the non-semantic instruction set itself.
-
Restrictions (informational):
- OpTypeSampledImage and OpSampledImage do not work on Buffer images.
- OpBranchConditional cannot have the same id for the True Lable and False Label.
- Dominant language
- C++
- Stars
- 234
- Forks
- 240
- Avg merge
- 6d 12h
- Merged PRs (30d)
- 15
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from KhronosGroup/OpenCL-CTS
-
cognizant-backlog
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
KhronosGroup/OpenCL-CTS#2882 · 1 comment ·
Maintainers usually reply within 1 day
-
cl_khr_command_buffer: negative_enqueue_inconsistent_device expects CL_INCOMPATIBLE_COMMAND_QUEUE_KHR instead of CL_INVALID_DEVICEPossibly taken @kpet claimed this 11 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
KhronosGroup/OpenCL-CTS#2872 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
test_compiler: feature macros for cl_ext_float_atomics are not testedPossibly taken @shajder claimed this 10 days ago. Opencognizant-triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
KhronosGroup/OpenCL-CTS#2818 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
KhronosGroup/OpenCL-CTS#2699 · 1 comment ·
Maintainers usually reply within 1 day
-
cleanup/refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
KhronosGroup/OpenCL-CTS#2057 ·
Maintainers usually reply within 1 day
All issues in KhronosGroup/OpenCL-CTS
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ROCm/FastFlowLM#1057 ·
Maintainers usually reply within 1 day
-
documentation GPU low priority
Difficulty 1/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Simba-Avionic/srp#510 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
useless statementOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day