You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpUntypedAccessChainKHR, OpUntypedInBoundsAccessChainKHR, OpUntypedPtrAccessChainKHR, OpUntypedInBoundsPtrAccessChainKHR are analogue instructions to their "typed" versions of access chain instructions.
It seems the extension should have extend the rules for OpSpecConstantOp by allowing untyped access chain operands to also be accepted. The only restriction the specification has is about the scope of the Base which can be found in untyped instructions as well:
for the AccessChain named opcodes, their Base is allowed to be a global (module scope) OpVariable instruction.
The text was updated successfully, but these errors were encountered:
OpUntypedAccessChainKHR
,OpUntypedInBoundsAccessChainKHR
,OpUntypedPtrAccessChainKHR
,OpUntypedInBoundsPtrAccessChainKHR
are analogue instructions to their "typed" versions of access chain instructions.It seems the extension should have extend the rules for
OpSpecConstantOp
by allowing untyped access chain operands to also be accepted. The only restriction the specification has is about the scope of theBase
which can be found in untyped instructions as well:The text was updated successfully, but these errors were encountered: