diff options
| author | drblallo <blalloscompany@gmail.com> | 2024-01-04 10:28:12 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-01-04 10:28:12 +0100 |
| commit | 2bd6642533ce858c07f1c412e1b8a669c17afb54 (patch) | |
| tree | 0e590054a34c48f54fc14fa9507700ddb815dfcb /llvm/lib/CodeGen/TargetLoweringBase.cpp | |
| parent | 7954c57124b495fbdc73674d71f2e366e4afe522 (diff) | |
| download | llvm-2bd6642533ce858c07f1c412e1b8a669c17afb54.zip llvm-2bd6642533ce858c07f1c412e1b8a669c17afb54.tar.gz llvm-2bd6642533ce858c07f1c412e1b8a669c17afb54.tar.bz2 | |
[mlir][dataflow]Fix dense backward dataflow intraprocedural hook (#76865)
The dataflow analysis framework within MLIR allows to customize the
transfer function when a `call-like` operation is encuntered.
The check to see if the analysis was executed in intraprocedural mode
was executed after the check to see if the callee had the
CallableOpInterface, and thus intraprocedural analyses would behave as
interpocedural ones when performing indirect calls.
This commit fixes the issue by performing the check for
intraprocedurality first.
Dense forward analyses were already behaving correctly.
https://github.com/llvm/llvm-project/blob/main/mlir/lib/Analysis/DataFlow/DenseAnalysis.cpp#L63
Co-authored-by: massimo <mo.fioravanti@gmail.com>
Diffstat (limited to 'llvm/lib/CodeGen/TargetLoweringBase.cpp')
0 files changed, 0 insertions, 0 deletions