diff options
author | Bill Wendling <isanbard@gmail.com> | 2011-08-17 20:36:44 +0000 |
---|---|---|
committer | Bill Wendling <isanbard@gmail.com> | 2011-08-17 20:36:44 +0000 |
commit | a9ee09f4be8b073e88f573eac520dcc8550034dc (patch) | |
tree | ee458e75afa905a9041568b9a85272f40a02d0cc /llvm/lib/VMCore/Instruction.cpp | |
parent | e41124ade18ac99f2453586dfa1de4b6973b78d7 (diff) | |
download | bcm5719-llvm-a9ee09f4be8b073e88f573eac520dcc8550034dc.tar.gz bcm5719-llvm-a9ee09f4be8b073e88f573eac520dcc8550034dc.zip |
Revert r137655. There is some question about whether the 'landingpad'
instruction should be marked as potentially reading and/or writing memory.
llvm-svn: 137863
Diffstat (limited to 'llvm/lib/VMCore/Instruction.cpp')
-rw-r--r-- | llvm/lib/VMCore/Instruction.cpp | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/llvm/lib/VMCore/Instruction.cpp b/llvm/lib/VMCore/Instruction.cpp index 863b098e8f8..f54cec11e2e 100644 --- a/llvm/lib/VMCore/Instruction.cpp +++ b/llvm/lib/VMCore/Instruction.cpp @@ -320,7 +320,6 @@ bool Instruction::mayReadFromMemory() const { case Instruction::Fence: // FIXME: refine definition of mayReadFromMemory case Instruction::AtomicCmpXchg: case Instruction::AtomicRMW: - case Instruction::LandingPad: return true; case Instruction::Call: return !cast<CallInst>(this)->doesNotAccessMemory(); @@ -341,7 +340,6 @@ bool Instruction::mayWriteToMemory() const { case Instruction::VAArg: case Instruction::AtomicCmpXchg: case Instruction::AtomicRMW: - case Instruction::LandingPad: return true; case Instruction::Call: return !cast<CallInst>(this)->onlyReadsMemory(); |