From 0977d4d4df7b3cee9cecfa696df15016ba38eb1b Mon Sep 17 00:00:00 2001 From: Sanjoy Das Date: Sat, 21 Nov 2015 09:12:07 +0000 Subject: [PATCH] [docs] Minor fixes to the operand bundle section git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@253771 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/LangRef.rst | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/LangRef.rst b/docs/LangRef.rst index cd1fb01c652..c7ea1c1bf23 100644 --- a/docs/LangRef.rst +++ b/docs/LangRef.rst @@ -1457,7 +1457,7 @@ incorrect and will change program semantics. Syntax:: - operand bundle set ::= '[' operand bundle ']' + operand bundle set ::= '[' operand bundle (, operand bundle )* ']' operand bundle ::= tag '(' [ bundle operand ] (, bundle operand )* ')' bundle operand ::= SSA value tag ::= string constant @@ -1493,13 +1493,14 @@ More specific types of operand bundles are described below. Deoptimization Operand Bundles ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Deoptimization operand bundles are characterized by the ``"deopt`` +Deoptimization operand bundles are characterized by the ``"deopt"`` operand bundle tag. These operand bundles represent an alternate "safe" continuation for the call site they're attached to, and can be used by a suitable runtime to deoptimize the compiled frame at the -specified call site. Exact details of deoptimization is out of scope -for the language reference, but it usually involves rewriting a -compiled frame into a set of interpreted frames. +specified call site. There can be at most one ``"deopt"`` operand +bundle attached to a call site. Exact details of deoptimization is +out of scope for the language reference, but it usually involves +rewriting a compiled frame into a set of interpreted frames. From the compiler's perspective, deoptimization operand bundles make the call sites they're attached to at least ``readonly``. They read -- 2.34.1