diff options
author | Jeremy Kun <jkun@google.com> | 2025-06-20 08:16:52 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2025-06-20 08:16:52 -0700 |
commit | b533b0ec34ac36d8a6af406d1fb046e07f95f717 (patch) | |
tree | 100e4350862efbcd428c695ca71e0bfcf0f69655 /clang/lib/AST/ByteCode | |
parent | 71e20c6c86e04863df80e286a004a20070a5a610 (diff) | |
download | llvm-b533b0ec34ac36d8a6af406d1fb046e07f95f717.zip llvm-b533b0ec34ac36d8a6af406d1fb046e07f95f717.tar.gz llvm-b533b0ec34ac36d8a6af406d1fb046e07f95f717.tar.bz2 |
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>
Diffstat (limited to 'clang/lib/AST/ByteCode')
0 files changed, 0 insertions, 0 deletions