[spirv] Remove one level of indirection: processOp to processOpImpl
authorLei Zhang <antiagainst@google.com>
Mon, 22 Jul 2019 12:37:12 +0000 (05:37 -0700)
committerA. Unique TensorFlower <gardener@tensorflow.org>
Mon, 22 Jul 2019 12:37:39 +0000 (05:37 -0700)
commit17c18840dabfa894d1ac90146469680d3750a8b6
tree029cac9d581828fd7abb1df74aa051cacec4bbf0
parent48a1baeb8a588fa466abb861b960463236ca3016
[spirv] Remove one level of indirection: processOp to processOpImpl

We already have two levels of controls in SPIRVBase.td: hasOpcode and
autogenSerialization. The former controls whether to add an entry to
the dispatch table, while the latter controls whether to autogenerate
the op's (de)serialization method specialization. This is enough for
our cases. Remove the indirection from processOp to processOpImpl
to simplify the picture.

PiperOrigin-RevId: 259308711
mlir/include/mlir/Dialect/SPIRV/SPIRVBase.td
mlir/lib/Dialect/SPIRV/Serialization/Deserializer.cpp
mlir/lib/Dialect/SPIRV/Serialization/Serializer.cpp
mlir/tools/mlir-tblgen/SPIRVUtilsGen.cpp