aboutsummaryrefslogtreecommitdiffhomepage
path: root/tensorflow/compiler/xla/service/hlo_value.cc
diff options
context:
space:
mode:
authorGravatar A. Unique TensorFlower <gardener@tensorflow.org>2018-09-19 08:20:47 -0700
committerGravatar TensorFlower Gardener <gardener@tensorflow.org>2018-09-19 08:26:55 -0700
commit42832c2d44ae1845354afed2c22841555645ebe8 (patch)
tree69c2dab01421741cbd6bc9e34f6d0c6c5a11ce4a /tensorflow/compiler/xla/service/hlo_value.cc
parente00d7744dbab5c73e4d8ffa8a7d361f7b2dcefff (diff)
Treat kDomain instruction as a pure pass-through in HloValue
It doesn't access the data in any way similarly to kTuple so it should be handled the same way. PiperOrigin-RevId: 213630620
Diffstat (limited to 'tensorflow/compiler/xla/service/hlo_value.cc')
-rw-r--r--tensorflow/compiler/xla/service/hlo_value.cc1
1 files changed, 1 insertions, 0 deletions
diff --git a/tensorflow/compiler/xla/service/hlo_value.cc b/tensorflow/compiler/xla/service/hlo_value.cc
index 773fc7d225..8549487702 100644
--- a/tensorflow/compiler/xla/service/hlo_value.cc
+++ b/tensorflow/compiler/xla/service/hlo_value.cc
@@ -131,6 +131,7 @@ bool MayUseOperandValue(int64 operand_number, const ShapeIndex& index,
CHECK_LE(operand_number, 2);
return operand_number == 0 || index.empty();
+ case HloOpcode::kDomain:
case HloOpcode::kTuple:
// These instructions always pass through their operands transparently.
return false;