Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SPIR-V 1.4 Testing #2120

Closed
21 tasks done
bashbaug opened this issue Oct 17, 2024 · 5 comments
Closed
21 tasks done

SPIR-V 1.4 Testing #2120

bashbaug opened this issue Oct 17, 2024 · 5 comments

Comments

@bashbaug
Copy link
Contributor

bashbaug commented Oct 17, 2024

This issue is intended to track testing for SPIR-V 1.4 features.

@bashbaug
Copy link
Contributor Author

Testing for OpCopyMemory with two optional memory operands is on hold due to issues in the SPIR-V LLVM Translator, see KhronosGroup/SPIRV-LLVM-Translator#2769.

@bashbaug
Copy link
Contributor Author

Testing OpCopyLogical is on hold due to issues in the SPIR-V LLVM Translator, see KhronosGroup/SPIRV-LLVM-Translator#2768.

@bashbaug
Copy link
Contributor Author

Regarding the last item without a PR - OpSpecConstantOp support for OpUConvert - here are several possible options:

  1. I can add a targeted test for just OpUConvert.
  2. We can ensure this case gets tested as part of the resolution for Missing Testing for OpSpecConstantOp #2137.

@svenvh
Copy link
Member

svenvh commented Nov 25, 2024

Regarding the last item without a PR - OpSpecConstantOp support for OpUConvert - here are several possible options:

  1. I can add a targeted test for just OpUConvert.
  2. We can ensure this case gets tested as part of the resolution for Missing Testing for OpSpecConstantOp #2137.

This isn't new functionality in "Kernel-flavour" SPIR-V 1.4 it seems. The SPIR-V specification says this for OpSpecConstantOp:

If the Kernel capability was declared, the following opcodes are also valid: ..., OpUConvert,

OpUConvert support for OpSpecConstantOp seems only new in SPIR-V 1.4 for graphics, also confirmed by the internal Khronos SPIR-V Issue 156.

So option 2 from your list sounds reasonable to me.

@bashbaug
Copy link
Contributor Author

Cool, I think all tasks are complete then, so I am closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants