| commit | 0fa73c93f9516e19a04c7e6e89c5da97e312fcee | [log] [tgz] |
|---|---|---|
| author | Jeremy Kun <jkun@google.com> | Fri Jun 20 08:16:52 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jun 20 08:20:49 2025 -0700 |
| tree | 159c0fd115d3b9b9f3b7472b7e8248473fe1b299 | |
| parent | 5cbe01e05d40739773a7d4af3c2c252620a20d3e [diff] |
Define a DataFlowSolver helper that loads sensible default analyses (#143415) Cf. https://discourse.llvm.org/t/mlir-dead-code-analysis/67568/10 Custom analysis passes will not work properly unless both DeadCodeAnalysis and SparseConstantPropagation are loaded to the DataFlowSolver. This is intended behavior, but surprising to many users as shown in the thread. In lieu of a longer-term fix (which I am not knowledgeable enough to implement myself, yet), this commit adds a helper function that loads these two analyses, as well as providing breadcrumbs for an explanation of the problem. The existing places in the codebase where these two analyses are loaded for the purpose of running other unrelated analyses are replaced by the use of the helper. --------- Co-authored-by: Jeremy Kun <j2kun@users.noreply.github.com> Co-authored-by: Oleksandr "Alex" Zinenko <azinenko@amd.com> GitOrigin-RevId: b533b0ec34ac36d8a6af406d1fb046e07f95f717
See https://mlir.llvm.org/ for more information.