maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

[DebugInfo][Docs] Fix RST syntax for DW_OP_LLVM_arg in LangRef 

The inline code in the description of `DW_OP_LLVM_arg` wasn't terminating
correctly, leading to more text displayed as code than intended. This fixes that
up and adds a superscript as a tiny embellishment.
This commit is contained in:
J. Ryan Stinnett 2022-09-12 12:43:17 +01:00
parent ea26ed1f9c
commit d635695cf8
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
llvm/docs/LangRef.rst
View File

@ -5813,7 +5813,7 @@ The current supported opcode vocabulary is limited:
- ``DW_OP_LLVM_arg, N`` is used in debug intrinsics that refer to more than one - ``DW_OP_LLVM_arg, N`` is used in debug intrinsics that refer to more than one
value, such as one that calculates the sum of two registers. This is always value, such as one that calculates the sum of two registers. This is always
used in combination with an ordered list of values, such that used in combination with an ordered list of values, such that
``DW_OP_LLVM_arg, N`` refers to the ``N``th element in that list. For ``DW_OP_LLVM_arg, N`` refers to the ``N``\ :sup:`th` element in that list. For
example, ``!DIExpression(DW_OP_LLVM_arg, 0, DW_OP_LLVM_arg, 1, DW_OP_minus, example, ``!DIExpression(DW_OP_LLVM_arg, 0, DW_OP_LLVM_arg, 1, DW_OP_minus,
DW_OP_stack_value)`` used with the list ``(%reg1, %reg2)`` would evaluate to DW_OP_stack_value)`` used with the list ``(%reg1, %reg2)`` would evaluate to
``%reg1 - reg2``. This list of values should be provided by the containing ``%reg1 - reg2``. This list of values should be provided by the containing