This repository has been archived by the owner on Oct 9, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 60
OpSource should allow optional string operand for source code #12
Comments
yxsamliu
changed the title
OpSource will allow optional string operand for source code
OpSource should allow optional string operand for source code
Dec 1, 2015
echuraev
added a commit
to echuraev/SPIRV-LLVM
that referenced
this issue
Sep 26, 2016
In one of last change of spirv spec was added following change: "Public SPIRV-Headers issues KhronosGroup#12 and KhronosGroup#13 and Khronos SPIR-V issue KhronosGroup#65: Allow OpVariable as an initializer for another OpVariable instruction or the Base of an OpSpecConstantOp with an AccessChain opcode." In this way, OpVariable can be initialize before OpSpecConstantOp. To do this, it's necessary add OpSpecConstantOp in one container with OpVariable in TopologicalSort. After this change, OpSpecConstantOp and OpVariable instructions will be add to spirv file in the right order.
yxsamliu
pushed a commit
that referenced
this issue
Sep 29, 2016
* Fixed problem with OpSpecConstantOp. In one of last change of spirv spec was added following change: "Public SPIRV-Headers issues #12 and #13 and Khronos SPIR-V issue #65: Allow OpVariable as an initializer for another OpVariable instruction or the Base of an OpSpecConstantOp with an AccessChain opcode." In this way, OpVariable can be initialize before OpSpecConstantOp. To do this, it's necessary add OpSpecConstantOp in one container with OpVariable in TopologicalSort. After this change, OpSpecConstantOp and OpVariable instructions will be add to spirv file in the right order. * Renamed InstructionVec to ConstAndVarVec and fixed indentation
3 tasks
robclark
pushed a commit
to freedreno/SPIRV-LLVM
that referenced
this issue
Jan 26, 2018
* Fixed problem with OpSpecConstantOp. In one of last change of spirv spec was added following change: "Public SPIRV-Headers issues KhronosGroup#12 and KhronosGroup#13 and Khronos SPIR-V issue KhronosGroup#65: Allow OpVariable as an initializer for another OpVariable instruction or the Base of an OpSpecConstantOp with an AccessChain opcode." In this way, OpVariable can be initialize before OpSpecConstantOp. To do this, it's necessary add OpSpecConstantOp in one container with OpVariable in TopologicalSort. After this change, OpSpecConstantOp and OpVariable instructions will be add to spirv file in the right order. * Renamed InstructionVec to ConstAndVarVec and fixed indentation
AlexeySotkin
pushed a commit
to AlexeySotkin/SPIRV-LLVM
that referenced
this issue
Mar 12, 2018
* Fixed problem with OpSpecConstantOp. In one of last change of spirv spec was added following change: "Public SPIRV-Headers issues KhronosGroup#12 and KhronosGroup#13 and Khronos SPIR-V issue KhronosGroup#65: Allow OpVariable as an initializer for another OpVariable instruction or the Base of an OpSpecConstantOp with an AccessChain opcode." In this way, OpVariable can be initialize before OpSpecConstantOp. To do this, it's necessary add OpSpecConstantOp in one container with OpVariable in TopologicalSort. After this change, OpSpecConstantOp and OpVariable instructions will be add to spirv file in the right order. * Renamed InstructionVec to ConstAndVarVec and fixed indentation
AlexeySotkin
pushed a commit
to AlexeySotkin/SPIRV-LLVM
that referenced
this issue
Apr 3, 2018
* Fixed problem with OpSpecConstantOp. In one of last change of spirv spec was added following change: "Public SPIRV-Headers issues KhronosGroup#12 and KhronosGroup#13 and Khronos SPIR-V issue KhronosGroup#65: Allow OpVariable as an initializer for another OpVariable instruction or the Base of an OpSpecConstantOp with an AccessChain opcode." In this way, OpVariable can be initialize before OpSpecConstantOp. To do this, it's necessary add OpSpecConstantOp in one container with OpVariable in TopologicalSort. After this change, OpSpecConstantOp and OpVariable instructions will be add to spirv file in the right order. * Renamed InstructionVec to ConstAndVarVec and fixed indentation
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
No description provided.
The text was updated successfully, but these errors were encountered: