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/pattern-multi-result-op.td

90 lines
2.9 KiB
TableGen
Raw Normal View History

Add UnitAttr in OpBase.td. Note that UnitAttr cannot be used for op definition yet. PiperOrigin-RevId: 258693338
2019-07-18 11:10:39 +08:00
// RUN: mlir-tblgen -gen-rewriters -I %S/../../include %s | FileCheck %s --dump-input-on-failure
[TableGen] Support multiple result patterns This CL added the ability to generate multiple ops using multiple result patterns, with each of them replacing one result of the matched source op. Specifically, the syntax is ``` def : Pattern<(SourceOp ...), [(ResultOp1 ...), (ResultOp2 ...), (ResultOp3 ...)]>; ``` Assuming `SourceOp` has three results. Currently we require that each result op must generate one result, which can be lifted later when use cases arise. To help with cases that certain output is unused and we don't care about it, this CL also introduces a new directive: `verifyUnusedValue`. Checks will be emitted in the `match()` method to make sure if the corresponding output is not unused, `match()` returns with `matchFailure()`. PiperOrigin-RevId: 237513904
2019-03-09 05:56:53 +08:00
include "mlir/IR/OpBase.td"
Add Dialect in op definition to capture prefix and documentation. Enables specifying the documentation for dialect along with defining the ops of the dialect. The doc generator will be expanded in follow up to emit the documentation in the autogenerated files. This is precursor to allowing common base for all ops in a dialect. All the dialect documentation is super sparse and just added as placeholder. I was tempted (and started) to move ConstantOp to be generated too, but this will be easier post adding extra_methods, so deferring until then. -- PiperOrigin-RevId: 245759984
2019-04-30 00:24:09 +08:00
def Test_Dialect : Dialect {
let name = "test";
[ODS] Allow dialect to specify C++ namespaces Previously we force the C++ namespaces to be `NS` if `SomeOp` is defined as `NS_SomeOp`. This is too rigid as it does not support nested namespaces well. This CL adds a "namespace" field into the Dialect class to allow flexible namespaces. -- PiperOrigin-RevId: 249064981
2019-05-21 00:33:10 +08:00
let cppNamespace = "";
Add Dialect in op definition to capture prefix and documentation. Enables specifying the documentation for dialect along with defining the ops of the dialect. The doc generator will be expanded in follow up to emit the documentation in the autogenerated files. This is precursor to allowing common base for all ops in a dialect. All the dialect documentation is super sparse and just added as placeholder. I was tempted (and started) to move ConstantOp to be generated too, but this will be easier post adding extra_methods, so deferring until then. -- PiperOrigin-RevId: 245759984
2019-04-30 00:24:09 +08:00
}
class NS_Op<string mnemonic, list<OpTrait> traits> :
Op<Test_Dialect, mnemonic, traits>;
def ThreeResultOp : NS_Op<"three_result_op", []> {
[TableGen] Support multiple result patterns This CL added the ability to generate multiple ops using multiple result patterns, with each of them replacing one result of the matched source op. Specifically, the syntax is ``` def : Pattern<(SourceOp ...), [(ResultOp1 ...), (ResultOp2 ...), (ResultOp3 ...)]>; ``` Assuming `SourceOp` has three results. Currently we require that each result op must generate one result, which can be lifted later when use cases arise. To help with cases that certain output is unused and we don't care about it, this CL also introduces a new directive: `verifyUnusedValue`. Checks will be emitted in the `match()` method to make sure if the corresponding output is not unused, `match()` returns with `matchFailure()`. PiperOrigin-RevId: 237513904
2019-03-09 05:56:53 +08:00
let arguments = (ins I32:$input);
let results = (outs I32:$r1, I32:$r2, I32:$r3);
}
Add Dialect in op definition to capture prefix and documentation. Enables specifying the documentation for dialect along with defining the ops of the dialect. The doc generator will be expanded in follow up to emit the documentation in the autogenerated files. This is precursor to allowing common base for all ops in a dialect. All the dialect documentation is super sparse and just added as placeholder. I was tempted (and started) to move ConstantOp to be generated too, but this will be easier post adding extra_methods, so deferring until then. -- PiperOrigin-RevId: 245759984
2019-04-30 00:24:09 +08:00
def TwoResultOp : NS_Op<"two_result_op", []> {
[TableGen] Allow additional result patterns not directly used for replacement This CL looses the requirement that all result patterns in a rewrite rule must replace a result of the root op in the source pattern. Now only the last N result pattern-generated ops are used to replace a N-result source op. This allows to generate additional ops to aid building up final ops used to replace the source op. -- PiperOrigin-RevId: 241783192
2019-04-04 03:29:14 +08:00
let arguments = (ins I32:$input);
let results = (outs I32:$r1, I32:$r2);
}
Add Dialect in op definition to capture prefix and documentation. Enables specifying the documentation for dialect along with defining the ops of the dialect. The doc generator will be expanded in follow up to emit the documentation in the autogenerated files. This is precursor to allowing common base for all ops in a dialect. All the dialect documentation is super sparse and just added as placeholder. I was tempted (and started) to move ConstantOp to be generated too, but this will be easier post adding extra_methods, so deferring until then. -- PiperOrigin-RevId: 245759984
2019-04-30 00:24:09 +08:00
def OneResultOp : NS_Op<"one_result_op", []> {
[TableGen] Support multiple result patterns This CL added the ability to generate multiple ops using multiple result patterns, with each of them replacing one result of the matched source op. Specifically, the syntax is ``` def : Pattern<(SourceOp ...), [(ResultOp1 ...), (ResultOp2 ...), (ResultOp3 ...)]>; ``` Assuming `SourceOp` has three results. Currently we require that each result op must generate one result, which can be lifted later when use cases arise. To help with cases that certain output is unused and we don't care about it, this CL also introduces a new directive: `verifyUnusedValue`. Checks will be emitted in the `match()` method to make sure if the corresponding output is not unused, `match()` returns with `matchFailure()`. PiperOrigin-RevId: 237513904
2019-03-09 05:56:53 +08:00
let arguments = (ins I32:$input);
let results = (outs I32:$r1);
}
Move the definitions for CallOp and IndirectCallOp to the Op Definition Generator. -- PiperOrigin-RevId: 247686419
2019-05-11 06:27:34 +08:00
def b : Pattern<(ThreeResultOp $input), [
[TableGen] Change to attach the name to DAG operator in result patterns There are two ways that we can attach a name to a DAG node: 1) (Op:$name ...) 2) (Op ...):$name The problem with 2) is that we cannot do it on the outmost DAG node in a tree. Switch from 2) to 1). PiperOrigin-RevId: 237513962
2019-03-09 05:57:09 +08:00
(OneResultOp (OneResultOp:$interm $input)),
(OneResultOp $interm),
(OneResultOp (OneResultOp $interm))
]>;
Move the definitions for CallOp and IndirectCallOp to the Op Definition Generator. -- PiperOrigin-RevId: 247686419
2019-05-11 06:27:34 +08:00
// CHECK-LABEL: struct b
[TableGen] Change to attach the name to DAG operator in result patterns There are two ways that we can attach a name to a DAG node: 1) (Op:$name ...) 2) (Op ...):$name The problem with 2) is that we cannot do it on the outmost DAG node in a tree. Switch from 2) to 1). PiperOrigin-RevId: 237513962
2019-03-09 05:57:09 +08:00
// CHECK: void rewrite(
// CHECK: auto interm = rewriter.create<OneResultOp>(
// CHECK-NEXT: /*input=*/s.input
// CHECK: auto vOneResultOp0 = rewriter.create<OneResultOp>(
// CHECK-NEXT: /*input=*/interm
// CHECK: auto vOneResultOp1 = rewriter.create<OneResultOp>(
// CHECK-NEXT: /*input=*/interm
// CHECK: auto vOneResultOp2 = rewriter.create<OneResultOp>(
// CHECK-NEXT: /*input=*/interm
// CHECK: auto vOneResultOp3 = rewriter.create<OneResultOp>(
// CHECK-NEXT: /*input=*/vOneResultOp2
[TableGen] Support creating multi-result ops in result patterns This CL introduces a new syntax for creating multi-result ops and access their results in result patterns. Specifically, if a multi-result op is unbound or bound to a name without a trailing `__N` suffix, it will act as a value pack and expand to all its values. If a multi-result op is bound to a symbol with `__N` suffix, only the N-th result will be extracted and used. PiperOrigin-RevId: 256465208
2019-07-04 08:17:33 +08:00
// CHECK: rewriter.replaceOp(op, {vOneResultOp0.getOperation()->getResult(0), vOneResultOp1.getOperation()->getResult(0), vOneResultOp3.getOperation()->getResult(0)});
[TableGen] Change to attach the name to DAG operator in result patterns There are two ways that we can attach a name to a DAG node: 1) (Op:$name ...) 2) (Op ...):$name The problem with 2) is that we cannot do it on the outmost DAG node in a tree. Switch from 2) to 1). PiperOrigin-RevId: 237513962
2019-03-09 05:57:09 +08:00
[TableGen] Allow additional result patterns not directly used for replacement This CL looses the requirement that all result patterns in a rewrite rule must replace a result of the root op in the source pattern. Now only the last N result pattern-generated ops are used to replace a N-result source op. This allows to generate additional ops to aid building up final ops used to replace the source op. -- PiperOrigin-RevId: 241783192
2019-04-04 03:29:14 +08:00
// Test more result patterns than needed for replacement
// ---
Add Dialect in op definition to capture prefix and documentation. Enables specifying the documentation for dialect along with defining the ops of the dialect. The doc generator will be expanded in follow up to emit the documentation in the autogenerated files. This is precursor to allowing common base for all ops in a dialect. All the dialect documentation is super sparse and just added as placeholder. I was tempted (and started) to move ConstantOp to be generated too, but this will be easier post adding extra_methods, so deferring until then. -- PiperOrigin-RevId: 245759984
2019-04-30 00:24:09 +08:00
def AdditionalOp : NS_Op<"additional_one_result_op", []> {
[TableGen] Allow additional result patterns not directly used for replacement This CL looses the requirement that all result patterns in a rewrite rule must replace a result of the root op in the source pattern. Now only the last N result pattern-generated ops are used to replace a N-result source op. This allows to generate additional ops to aid building up final ops used to replace the source op. -- PiperOrigin-RevId: 241783192
2019-04-04 03:29:14 +08:00
let arguments = (ins I32:$input);
let results = (outs I32:$r1);
}
Move the definitions for CallOp and IndirectCallOp to the Op Definition Generator. -- PiperOrigin-RevId: 247686419
2019-05-11 06:27:34 +08:00
def c : Pattern<(TwoResultOp $input), [
[TableGen] Allow additional result patterns not directly used for replacement This CL looses the requirement that all result patterns in a rewrite rule must replace a result of the root op in the source pattern. Now only the last N result pattern-generated ops are used to replace a N-result source op. This allows to generate additional ops to aid building up final ops used to replace the source op. -- PiperOrigin-RevId: 241783192
2019-04-04 03:29:14 +08:00
// Additional op generated to help build the final result but not
// directly used to replace the source op
(AdditionalOp:$interm $input),
(OneResultOp $interm),
(OneResultOp $input)
]>;
Move the definitions for CallOp and IndirectCallOp to the Op Definition Generator. -- PiperOrigin-RevId: 247686419
2019-05-11 06:27:34 +08:00
// CHECK-LABEL: struct c
[TableGen] Allow additional result patterns not directly used for replacement This CL looses the requirement that all result patterns in a rewrite rule must replace a result of the root op in the source pattern. Now only the last N result pattern-generated ops are used to replace a N-result source op. This allows to generate additional ops to aid building up final ops used to replace the source op. -- PiperOrigin-RevId: 241783192
2019-04-04 03:29:14 +08:00
// CHECK: auto interm = rewriter.create<AdditionalOp>(
// CHECK: auto vOneResultOp0 = rewriter.create<OneResultOp>(
// CHECK-NEXT: /*input=*/interm
// CHECK: auto vOneResultOp1 = rewriter.create<OneResultOp>(
[TableGen] Support creating multi-result ops in result patterns This CL introduces a new syntax for creating multi-result ops and access their results in result patterns. Specifically, if a multi-result op is unbound or bound to a name without a trailing `__N` suffix, it will act as a value pack and expand to all its values. If a multi-result op is bound to a symbol with `__N` suffix, only the N-th result will be extracted and used. PiperOrigin-RevId: 256465208
2019-07-04 08:17:33 +08:00
// CHECK: rewriter.replaceOp(op, {vOneResultOp0.getOperation()->getResult(0), vOneResultOp1.getOperation()->getResult(0)});
Add UnitAttr in OpBase.td. Note that UnitAttr cannot be used for op definition yet. PiperOrigin-RevId: 258693338
2019-07-18 11:10:39 +08:00
// Test UnitAttr in rewrite patterns
// ---
def UnitAttrOp : NS_Op<"unit_attr_op", []> {
let arguments = (ins AnyAttr:$value);
let results = (outs NoneType:$output);
}
def NoneOp : NS_Op<"none_op", []> {
let results = (outs NoneType:$output);
}
def d : Pat<(UnitAttrOp UnitAttr:$ignore),
(NoneOp)>;
// CHECK-LABEL: struct d
// CHECK: PatternMatchResult match(Operation *op0) const override {
// CHECK: if (!((attr.isa<UnitAttr>()))) return matchFailure();