From f20480461a21ee7efceada6b4f436593c2983bdd Mon Sep 17 00:00:00 2001 From: Philip Reames Date: Thu, 4 Mar 2021 15:18:11 -0800 Subject: [PATCH] [docs] Remove some stale wording from gc.relocate description We dropped support for the non-bundle form a while back, but I apparently missed updating one place in the docs. --- llvm/docs/LangRef.rst | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/llvm/docs/LangRef.rst b/llvm/docs/LangRef.rst index 543ac84d8453..be8e6da356a5 100644 --- a/llvm/docs/LangRef.rst +++ b/llvm/docs/LangRef.rst @@ -11934,13 +11934,8 @@ safepoint sequence of which this ``gc.relocation`` is a part. Despite the typing of this as a generic token, *only* the value defined by a ``gc.statepoint`` is legal here. -The second and third arguments are both indices into operands of their -corresponding statepoint. If the statepoint has a :ref:`gc-live ` -operand bundle, then both arguments are indices into the operand bundle's -operands. If there is no "gc-live" bundle, then the index is into the -statepoint's list of arguments. This index must land within the 'gc -parameter' section of the statepoint's argument list. Use of the "gc-live" -form is recommended. +The second and third arguments are both indices into operands of the +corresponding statepoint's :ref:`gc-live ` operand bundle. The second argument is an index which specifies the allocation for the pointer being relocated. The associated value must be within the object with which the