maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/mlir/test/mlir-tblgen/op-operand.td

13 lines
444 B
TableGen
Raw Normal View History

[TableGen] Generate op declaration and definition into different files Previously we emit both op declaration and definition into one file and include it in *Ops.h. That pulls in lots of implementation details in the header file and we cannot hide symbols local to implementation. This CL splits them to provide a cleaner interface. The way how we define custom builders in TableGen is changed accordingly because now we need to distinguish signatures and implementation logic. Some custom builders with complicated logic now can be moved to be implemented in .cpp entirely. PiperOrigin-RevId: 239509594
2019-03-21 08:25:34 +08:00
// RUN: mlir-tblgen -gen-op-defs -I %S/../../include %s | FileCheck %s
[TableGen] Emit verification code for op results They can be verified using the same logic as operands. PiperOrigin-RevId: 237101461
2019-03-07 04:50:01 +08:00
include "mlir/IR/OpBase.td"
def OneOperandOp : Op<"one_operand_op", []> {
let arguments = (ins I32:$input);
}
[TableGen] Generate op declaration and definition into different files Previously we emit both op declaration and definition into one file and include it in *Ops.h. That pulls in lots of implementation details in the header file and we cannot hide symbols local to implementation. This CL splits them to provide a cleaner interface. The way how we define custom builders in TableGen is changed accordingly because now we need to distinguish signatures and implementation logic. Some custom builders with complicated logic now can be moved to be implemented in .cpp entirely. PiperOrigin-RevId: 239509594
2019-03-21 08:25:34 +08:00
// CHECK-LABEL: OneOperandOp definitions
// CHECK: bool OneOperandOp::verify() const {
// CHECK: if (!((this->getInstruction()->getOperand(0)->getType().isInteger(32))))
[TableGen] Emit verification code for op results They can be verified using the same logic as operands. PiperOrigin-RevId: 237101461
2019-03-07 04:50:01 +08:00
// CHECK-NEXT: return emitOpError("operand #0 must be 32-bit integer");