diff options
| author | Nikita Popov <npopov@redhat.com> | 2022-12-09 15:29:35 +0100 |
|---|---|---|
| committer | Nikita Popov <npopov@redhat.com> | 2022-12-12 09:47:30 +0100 |
| commit | 243acd5dcbc637e477062877185ad76d8ff63d9d (patch) | |
| tree | 01c4556875b8d8cf63a0a8f90b3448d3384afc69 /llvm/lib/ProfileData/Coverage/CoverageMappingReader.cpp | |
| parent | 2f8cdea36d97b78ebc7e6f8d79ec9d69a4c503aa (diff) | |
| download | llvm-243acd5dcbc637e477062877185ad76d8ff63d9d.zip llvm-243acd5dcbc637e477062877185ad76d8ff63d9d.tar.gz llvm-243acd5dcbc637e477062877185ad76d8ff63d9d.tar.bz2 | |
[BasicAA] Remove support for PhiValues analysis
BasicAA currently has an optional dependency on the PhiValues
analysis. However, at least with our current pipeline setup, we
never actually make use of it. It's possible that this used to work
with the legacy pass manager, but I'm not sure of that either.
Given that this analysis has not actually been in use for a long
time, and nobody noticed or complained, I think we should drop
support for it and focus on one code path. It is worth noting that
analysis quality for the non-PhiValues case has significantly
improved in the meantime.
If we really wanted to make use of PhiValues, the right way would
probably be to pass it in via AAQI in places we want to use it,
rather than using an optional pass manager dependency (which are
an unpredictable PITA and should really only ever be used for
analyses that are only preserved and not used).
Differential Revision: https://reviews.llvm.org/D139719
Diffstat (limited to 'llvm/lib/ProfileData/Coverage/CoverageMappingReader.cpp')
0 files changed, 0 insertions, 0 deletions