From 61da47f19bfc6f348009b08ad432f1916d7e9008 Mon Sep 17 00:00:00 2001
From: Sanjoy Das <sanjoy@playingwithpointers.com>
Date: Fri, 23 Oct 2015 01:28:05 +0000
Subject: [PATCH] [LangRef] Fix the doc for operand bundles

I accidentally messed this up after a merge conflict in a previous
commit.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@251089 91177308-0d34-0410-b5e6-96231b3b80d8
---
 docs/LangRef.rst | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/docs/LangRef.rst b/docs/LangRef.rst
index 525b01c87ac..2a881d1d6d9 100644
--- a/docs/LangRef.rst
+++ b/docs/LangRef.rst
@@ -1473,14 +1473,6 @@ long as the behavior of an operand bundle is describable within these
 restrictions, LLVM does not need to have special knowledge of the
 operand bundle to not miscompile programs containing it.
 
-- The bundle operands for an unknown operand bundle escape in unknown
-  ways before control is transferred to the callee or invokee.
-- Calls and invokes with operand bundles have unknown read / write
-  effect on the heap on entry and exit (even if the call target is
-  ``readnone`` or ``readonly``).
-- An operand bundle at a call site cannot change the implementation
-  of the called function.  Inter-procedural optimizations work as
-  usual as long as they take into account the first two properties.
 - The bundle operands for an unknown operand bundle escape in unknown
   ways before control is transferred to the callee or invokee.
 - Calls and invokes with operand bundles have unknown read / write
-- 
2.40.0