Open MrSidims opened 6 months ago
Comments:
2 and 3. We can consider translating ptrtoint + cmp / sub
to these instructions during forward translation, but probably we should instead just recognize SPIR-V friendly input and then during reverse translation generate ptrtoint + cmp / sub
(either way with Builder::CreatePtrDiff)
Pretty much straightforward;
these decoration instructions are odd. I only see a single use-case for UserSemantic decorations for them, meanwhile the translator uses OpDecorate and OpMemberDecorate to store UserSemantic. And the translator is right in doing so as the spec puts no restrictions of what kind of literals to used for these 2 instructions;
The only thing left is to clarify the possible cases where we actually need to use DecorateString
and MemberDecorateString
instructions.
@MrSidims please link registry issue here once it's created. Thanks!
I created internal SPIR-V issue 810 to clarify OpDecorateString vs. OpDecorate, FYI.
Following my AR from OpenCL Tooling TSG. The translator claims SPIR-V 1.4 support, yet there are few features missing
OpCopyLogical
instructionOpPtrEqual
andOpPtrNotEqual
instructionsOpPtrDiff
instructionOpCopyMemory
andOpCopyMemorySized
instructions since 1.4 have optional Memory OperandsDecorateString
andOpMemberDecorateString
instructions