summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSanjoy Das <sanjoy@playingwithpointers.com>2015-10-23 01:28:05 +0000
committerSanjoy Das <sanjoy@playingwithpointers.com>2015-10-23 01:28:05 +0000
commit75d57fea49a1a212cdd50d328f4d26a5070f3599 (patch)
tree6f17ec5c5eed1398aec4517956b51760c92c2e31
parent4a8a8cde08b2616adf34ad9766d2dd811803ad8c (diff)
downloadbcm5719-llvm-75d57fea49a1a212cdd50d328f4d26a5070f3599.tar.gz
bcm5719-llvm-75d57fea49a1a212cdd50d328f4d26a5070f3599.zip
[LangRef] Fix the doc for operand bundles
I accidentally messed this up after a merge conflict in a previous commit. llvm-svn: 251089
-rw-r--r--llvm/docs/LangRef.rst8
1 files changed, 0 insertions, 8 deletions
diff --git a/llvm/docs/LangRef.rst b/llvm/docs/LangRef.rst
index 525b01c87ac..2a881d1d6d9 100644
--- a/llvm/docs/LangRef.rst
+++ b/llvm/docs/LangRef.rst
@@ -1477,14 +1477,6 @@ operand bundle to not miscompile programs containing it.
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
- effect on the heap on entry and exit (even if the call target is
``readnone`` or ``readonly``), unless they're overriden with
callsite specific attributes.
- An operand bundle at a call site cannot change the implementation
OpenPOWER on IntegriCloud