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 | c9b2a987a291434490fd5b3b6e98b9992916ece4 (patch) | |
| tree | 8d15e446ffe463064e51ba5b79d7c82ee90434a6 /lib/VMCore | |
| parent | 53727fc659af5f8fc51499fd875165533187d734 (diff) | |
| download | external_llvm-c9b2a987a291434490fd5b3b6e98b9992916ece4.zip external_llvm-c9b2a987a291434490fd5b3b6e98b9992916ece4.tar.gz external_llvm-c9b2a987a291434490fd5b3b6e98b9992916ece4.tar.bz2 | |
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/VMCore')
| -rw-r--r-- | lib/VMCore/Instruction.cpp | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/lib/VMCore/Instruction.cpp b/lib/VMCore/Instruction.cpp index 863b098..f54cec1 100644 --- a/lib/VMCore/Instruction.cpp +++ b/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(); |