]> granicus.if.org Git - llvm/commit
[LVI Printer] Rely on the LVI analysis functions rather than the LVI cache
authorAnna Thomas <anna@azul.com>
Tue, 6 Jun 2017 19:25:31 +0000 (19:25 +0000)
committerAnna Thomas <anna@azul.com>
Tue, 6 Jun 2017 19:25:31 +0000 (19:25 +0000)
commit46747f1821d0c2f07674b507008285146e827675
tree09410678d00e69721ee126886f9281c0699ae609
parent53a472fd29e990612d0174389eff58efa5d1f543
[LVI Printer] Rely on the LVI analysis functions rather than the LVI cache

Summary:
LVIPrinter pass was previously relying on the LVICache. We now directly call the
the LVI functions which solves the value if the LVI information is not already
available in the cache. This has 2 benefits over the printing of LVI cache:
1. higher coverage (i.e. catches errors) in LVI code when cache value is
invalidated.
2. relies on the core functions, and not dependent on the LVI cache (which may
be scrapped at some point).
It would still catch any cache invalidation errors, since we first go through
the cache.

Reviewers: reames, dberlin, sanjoy

Reviewed by: reames

Subscribers: llvm-commits

Differential Revision: https://reviews.llvm.org/D32135

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@304819 91177308-0d34-0410-b5e6-96231b3b80d8
include/llvm/Analysis/LazyValueInfo.h
lib/Analysis/LazyValueInfo.cpp
test/Analysis/LazyValueAnalysis/lvi-after-jumpthreading.ll