summaryrefslogtreecommitdiff
path: root/lib/Analysis/LoopInfo.cpp
diff options
context:
space:
mode:
authorBill Wendling <isanbard@gmail.com>2011-08-17 20:36:44 +0000
committerBill Wendling <isanbard@gmail.com>2011-08-17 20:36:44 +0000
commitc9b2a987a291434490fd5b3b6e98b9992916ece4 (patch)
tree8d15e446ffe463064e51ba5b79d7c82ee90434a6 /lib/Analysis/LoopInfo.cpp
parent53727fc659af5f8fc51499fd875165533187d734 (diff)
downloadllvm-c9b2a987a291434490fd5b3b6e98b9992916ece4.tar.gz
llvm-c9b2a987a291434490fd5b3b6e98b9992916ece4.tar.bz2
llvm-c9b2a987a291434490fd5b3b6e98b9992916ece4.tar.xz
Revert r137655. There is some question about whether the 'landingpad'
instruction should be marked as potentially reading and/or writing memory. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@137863 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'lib/Analysis/LoopInfo.cpp')
-rw-r--r--lib/Analysis/LoopInfo.cpp3
1 files changed, 3 insertions, 0 deletions
diff --git a/lib/Analysis/LoopInfo.cpp b/lib/Analysis/LoopInfo.cpp
index 9a7c50d7fa..36fd598d13 100644
--- a/lib/Analysis/LoopInfo.cpp
+++ b/lib/Analysis/LoopInfo.cpp
@@ -99,6 +99,9 @@ bool Loop::makeLoopInvariant(Instruction *I, bool &Changed,
return false;
if (I->mayReadFromMemory())
return false;
+ // The landingpad instruction is immobile.
+ if (isa<LandingPadInst>(I))
+ return false;
// Determine the insertion point, unless one was given.
if (!InsertPt) {
BasicBlock *Preheader = getLoopPreheader();