diff options
author | 2018-06-25 23:05:07 -0700 | |
---|---|---|
committer | 2018-06-25 23:08:42 -0700 | |
commit | 22c06a62b7dcc75f6f717cea63a947b21805afda (patch) | |
tree | 020fd0b07dad4994217170ba13624f15a3709feb /tensorflow/compiler/xla/service/hlo_graph_dumper.cc | |
parent | 5968eb87766d5536feefaaf8a9ee2f30aeadb354 (diff) |
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
Diffstat (limited to 'tensorflow/compiler/xla/service/hlo_graph_dumper.cc')
-rw-r--r-- | tensorflow/compiler/xla/service/hlo_graph_dumper.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tensorflow/compiler/xla/service/hlo_graph_dumper.cc b/tensorflow/compiler/xla/service/hlo_graph_dumper.cc index b349f7d46f..8856723f67 100644 --- a/tensorflow/compiler/xla/service/hlo_graph_dumper.cc +++ b/tensorflow/compiler/xla/service/hlo_graph_dumper.cc @@ -984,7 +984,7 @@ ColorScheme HloDotDumper::GetInstructionColor(const HloInstruction* instr) { case HloOpcode::kBitcast: case HloOpcode::kGetTupleElement: case HloOpcode::kTrace: - case HloOpcode::kGenerateToken: + case HloOpcode::kAfterAll: case HloOpcode::kTuple: return kWhite; case HloOpcode::kBroadcast: |