From 22c06a62b7dcc75f6f717cea63a947b21805afda Mon Sep 17 00:00:00 2001 From: Mark Heffernan Date: Mon, 25 Jun 2018 23:05:07 -0700 Subject: Rename HLO opcode kGenerateToken to kAfterAll. Long term I think we want to require kAfterAll to take at least one token as operand so it cannot generate a token out of thin air, so kGenerateToken is no longer an appropriate name. Instead, a primordial token would be supplied some how in the entry computation, perhaps as a parameter, and then threaded to any side-effecting ops. NFC. PiperOrigin-RevId: 202079040 --- tensorflow/compiler/xla/service/instruction_fusion.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tensorflow/compiler/xla/service/instruction_fusion.cc') diff --git a/tensorflow/compiler/xla/service/instruction_fusion.cc b/tensorflow/compiler/xla/service/instruction_fusion.cc index 9ac8635767..088cc26226 100644 --- a/tensorflow/compiler/xla/service/instruction_fusion.cc +++ b/tensorflow/compiler/xla/service/instruction_fusion.cc @@ -97,7 +97,7 @@ bool IsAlwaysDuplicable(const HloInstruction& instruction) { case HloOpcode::kShiftRightLogical: case HloOpcode::kSlice: case HloOpcode::kSubtract: - case HloOpcode::kGenerateToken: + case HloOpcode::kAfterAll: case HloOpcode::kTranspose: case HloOpcode::kTuple: return false; -- cgit v1.2.3