From: Dejan Mircevski <deki@google.com>
Date: Tue, 13 Oct 2015 18:41:31 +0000 (-0400)
Subject: Clarify handling of OperandImageOperands.
X-Git-Tag: upstream/2018.6~1511^2~43
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=f8e091af3db02800f0667777fcf136e82304e2d1;p=platform%2Fupstream%2FSPIRV-Tools.git

Clarify handling of OperandImageOperands.
---

diff --git a/source/opcode.cpp b/source/opcode.cpp
index 70f1ad7..d30d356 100644
--- a/source/opcode.cpp
+++ b/source/opcode.cpp
@@ -131,7 +131,9 @@ spv_operand_type_t convertOperandClassToType(spv::Op opcode,
       // It is not used as an operand.
       break;
     case OperandImageOperands:
-      // This is not used. It's only an artifact of spec generation.
+      // This is not used in opcode.inc. It only exists to generate the
+      // corresponding spec section. In parsing, image operands meld into the
+      // OperandOptionalImage case.
       break;
     case OperandFPFastMath: return SPV_OPERAND_TYPE_FP_FAST_MATH_MODE;
     case OperandFPRoundingMode: return SPV_OPERAND_TYPE_FP_ROUNDING_MODE;