diff options
| author | Kunwar Grover <groverkss@gmail.com> | 2025-03-06 08:41:47 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-03-06 08:41:47 +0000 |
| commit | 8e0a63ddad26c26501a7d9639b470665afadcf40 (patch) | |
| tree | ff87884e854c1722f02318d7a5726791ff53f467 /llvm/lib/CodeGen/AssignmentTrackingAnalysis.cpp | |
| parent | 6311e3fcc8539cf0f474b28f82a465e83013a792 (diff) | |
| download | llvm-8e0a63ddad26c26501a7d9639b470665afadcf40.zip llvm-8e0a63ddad26c26501a7d9639b470665afadcf40.tar.gz llvm-8e0a63ddad26c26501a7d9639b470665afadcf40.tar.bz2 | |
[mlir][docs] Add docs on canonicalizers being folders or patterns (#129517)
If a transformation should be a canonicalization is an orthogonal
question to if a transformation should be implemented as a
`RewritePattern` or a `fold` method. The later is an implementation
detail.
This patch adds a suggestion to always implement a canonicalization as a
`fold` pattern if possible, as they are a restricted subset of a
`RewritePattern`.
This has been a common source of confusion, as to when to implement a
canonicalization as a fold method or a RewritePattern.
Diffstat (limited to 'llvm/lib/CodeGen/AssignmentTrackingAnalysis.cpp')
0 files changed, 0 insertions, 0 deletions