[llvm] r251089 - [LangRef] Fix the doc for operand bundles
Sanjoy Das via llvm-commits
llvm-commits at lists.llvm.org
Thu Oct 22 18:28:05 PDT 2015
Author: sanjoy
Date: Thu Oct 22 20:28:05 2015
New Revision: 251089
URL: http://llvm.org/viewvc/llvm-project?rev=251089&view=rev
Log:
[LangRef] Fix the doc for operand bundles
I accidentally messed this up after a merge conflict in a previous
commit.
Modified:
llvm/trunk/docs/LangRef.rst
Modified: llvm/trunk/docs/LangRef.rst
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/LangRef.rst?rev=251089&r1=251088&r2=251089&view=diff
==============================================================================
--- llvm/trunk/docs/LangRef.rst (original)
+++ llvm/trunk/docs/LangRef.rst Thu Oct 22 20:28:05 2015
@@ -1477,14 +1477,6 @@ operand bundle to not miscompile program
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
More information about the llvm-commits
mailing list