I tried out the data flow analysis framework, and also realized the DeadCodeAnalysis was required for pretty much every analysis I wanted to do. So I’m sympathetic to making this easier to get started with, but I’m also curious what making it a “built-in” feature would entail. Maybe rather than built-in in the sense of “always included in DataFlowSolver” is too strong, but we could provide some helper that includes some sensible defaults (e.g. DeadCodeAnalysis and SparseConstantPropagation), which users could extend.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Some questions regarding deadcode analysis | 0 | 83 | September 8, 2025 | |
| SparseDataFlowAnalysis don't visit linalg.generic operation | 4 | 277 | September 13, 2023 | |
| Inspecting mlir dataflow analysis | 8 | 562 | January 4, 2024 | |
| Another guide on dataflow analysis in MLIR | 0 | 169 | June 2, 2025 | |
| [RFC] Add visitBranchPropertyArgument API to SparseDataFlowAnalysis and apply it in LivenessAnalysis/RemoveDeadValues/IntegerRangeAnalysis | 2 | 216 | December 27, 2025 |