SPIR-V 1.6 Testing

Open
#2,220 2 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
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
cpp

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

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.