aboutsummaryrefslogtreecommitdiff
path: root/llvm/utils/FileCheck/FileCheck.cpp
diff options
context:
space:
mode:
authorRiver Riddle <riddleriver@gmail.com>2022-01-02 03:41:08 +0000
committerRiver Riddle <riddleriver@gmail.com>2022-02-10 12:48:59 -0800
commitfaf42264e5401a1dfca95b701e5c2bf951d7f8a7 (patch)
tree79b585db4f47cc096750ac096edbb3eb1734f7cd /llvm/utils/FileCheck/FileCheck.cpp
parent3d8b90601211914b0d4690fa603e4b5c43e5c9ac (diff)
downloadllvm-faf42264e5401a1dfca95b701e5c2bf951d7f8a7.zip
llvm-faf42264e5401a1dfca95b701e5c2bf951d7f8a7.tar.gz
llvm-faf42264e5401a1dfca95b701e5c2bf951d7f8a7.tar.bz2
[PDLL] Add support for user defined constraint and rewrite functions
These functions allow for defining pattern fragments usable within the `match` and `rewrite` sections of a pattern. The main structure of Constraints and Rewrites functions are the same, and are similar to functions in other languages; they contain a signature (i.e. name, argument list, result list) and a body: ```pdll // Constraint that takes a value as an input, and produces a value: Constraint Cst(arg: Value) -> Value { ... } // Constraint that returns multiple values: Constraint Cst() -> (result1: Value, result2: ValueRange); ``` When returning multiple results, each result can be optionally be named (the result of a Constraint/Rewrite in the case of multiple results is a tuple). These body of a Constraint/Rewrite functions can be specified in several ways: * Externally In this case we are importing an external function (registered by the user outside of PDLL): ```pdll Constraint Foo(op: Op); Rewrite Bar(); ``` * In PDLL (using PDLL constructs) In this case, the body is defined using PDLL constructs: ```pdll Rewrite BuildFooOp() { // The result type of the Rewrite is inferred from the return. return op<my_dialect.foo>; } // Constraints/Rewrites can also implement a lambda/expression // body for simple one line bodies. Rewrite BuildFooOp() => op<my_dialect.foo>; ``` * In PDLL (using a native/C++ code block) In this case the body is specified using a C++(or potentially other language at some point) code block. When building PDLL in AOT mode this will generate a native constraint/rewrite and register it with the PDL bytecode. ```pdll Rewrite BuildFooOp() -> Op<my_dialect.foo> [{ return rewriter.create<my_dialect::FooOp>(...); }]; ``` Differential Revision: https://reviews.llvm.org/D115836
Diffstat (limited to 'llvm/utils/FileCheck/FileCheck.cpp')
0 files changed, 0 insertions, 0 deletions