aboutsummaryrefslogtreecommitdiff
path: root/llvm/unittests/Support/FileCheckTest.cpp
diff options
context:
space:
mode:
authorAlina Sbirlea <asbirlea@google.com>2019-06-19 21:33:09 +0000
committerAlina Sbirlea <asbirlea@google.com>2019-06-19 21:33:09 +0000
commit109d2ea1532ca88e0376fc8ad5d4f581ca616571 (patch)
tree8c37bfdb269c3e0cd9bcd994ac70847c06371ffb /llvm/unittests/Support/FileCheckTest.cpp
parent238b8e62b62da02cf779f735316e5749204af75c (diff)
downloadllvm-109d2ea1532ca88e0376fc8ad5d4f581ca616571.zip
llvm-109d2ea1532ca88e0376fc8ad5d4f581ca616571.tar.gz
llvm-109d2ea1532ca88e0376fc8ad5d4f581ca616571.tar.bz2
[MemorySSA] Cleanup trivial phis.
Summary: This is unfortunately needed for correctness, if we are to extend the tolerance of the update API to the way simple loop unswitch is doing cloning. In simple loop unswitch (as opposed to loop unswitch), not all blocks are cloned. This can create unreachable cloned blocks (no predecessor), which are later cleaned up. In MemorySSA, the APIs for supporting these kind of updates (clone + update exit blocks), make certain assumption on the integrity of the CFG. When cloning, if something was not cloned, it's values in MemorySSA default to LiveOnEntry. When updating exit blocks, it is safe to assume that we can first insert phis in the blocks merging two clones, then add additional phis in the IDF of the blocks that received phis. This no longer holds true if one of the clones being merged comes from an unreachable block. We'd conservatively need to add all phis before filling in their incoming definitions. In practice this restriction can be relaxed if we clean up trivial phis after the first round of insertion. Reviewers: george.burgess.iv Subscribers: jlebar, Prazek, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D63354 llvm-svn: 363880
Diffstat (limited to 'llvm/unittests/Support/FileCheckTest.cpp')
0 files changed, 0 insertions, 0 deletions