diff options
author | River Riddle <riddleriver@gmail.com> | 2022-03-19 15:08:09 -0700 |
---|---|---|
committer | River Riddle <riddleriver@gmail.com> | 2022-04-06 17:41:59 -0700 |
commit | ea64828a10e304f8131e40dfef062173fe606e6a (patch) | |
tree | 90402a42bf6fa8f712970292b1b2315c59c005a1 /llvm/lib/Target/WebAssembly/WebAssemblyTargetMachine.cpp | |
parent | f5e48a2ad3a96118dc95cdf2fd45337612a3b132 (diff) | |
download | llvm-ea64828a10e304f8131e40dfef062173fe606e6a.zip llvm-ea64828a10e304f8131e40dfef062173fe606e6a.tar.gz llvm-ea64828a10e304f8131e40dfef062173fe606e6a.tar.bz2 |
[mlir:PDL] Expand how native constraint/rewrite functions can be defined
This commit refactors the expected form of native constraint and rewrite
functions, and greatly reduces the necessary user complexity required when
defining a native function. Namely, this commit adds in automatic processing
of the necessary PDLValue glue code, and allows for users to define
constraint/rewrite functions using the C++ types that they actually want to
use.
As an example, lets see a simple example rewrite defined today:
```
static void rewriteFn(PatternRewriter &rewriter, PDLResultList &results,
ArrayRef<PDLValue> args) {
ValueRange operandValues = args[0].cast<ValueRange>();
TypeRange typeValues = args[1].cast<TypeRange>();
...
// Create an operation at some point and pass it back to PDL.
Operation *op = rewriter.create<SomeOp>(...);
results.push_back(op);
}
```
After this commit, that same rewrite could be defined as:
```
static Operation *rewriteFn(PatternRewriter &rewriter ValueRange operandValues,
TypeRange typeValues) {
...
// Create an operation at some point and pass it back to PDL.
return rewriter.create<SomeOp>(...);
}
```
Differential Revision: https://reviews.llvm.org/D122086
Diffstat (limited to 'llvm/lib/Target/WebAssembly/WebAssemblyTargetMachine.cpp')
0 files changed, 0 insertions, 0 deletions