[PATCH] D113631: [docs] Fix trailing whitespaces
Luís Ferreira via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Wed Nov 10 17:13:51 PST 2021
ljmf00 created this revision.
Herald added a subscriber: jdoerfert.
ljmf00 requested review of this revision.
Herald added a project: LLVM.
Herald added a subscriber: llvm-commits.
Repository:
rG LLVM Github Monorepo
https://reviews.llvm.org/D113631
Files:
llvm/docs/LangRef.rst
llvm/docs/SourceLevelDebugging.rst
Index: llvm/docs/SourceLevelDebugging.rst
===================================================================
--- llvm/docs/SourceLevelDebugging.rst
+++ llvm/docs/SourceLevelDebugging.rst
@@ -427,7 +427,7 @@
these potentially stale variable values from the developer diminishes the
amount of available debug information, but increases the reliability of the
remaining information.
-
+
To illustrate some potential issues, consider the following example:
.. code-block:: llvm
@@ -797,7 +797,7 @@
entry:
br i1 %cond, label %truebr, label %falsebr
- bb1:
+ bb1:
%value = phi i32 [ %value1, %truebr ], [ %value2, %falsebr ]
br label %exit, !dbg !26
@@ -813,7 +813,7 @@
%value = add i32 %input, 2
br label %bb1
- exit:
+ exit:
ret i32 %value, !dbg !30
}
@@ -1068,7 +1068,7 @@
.. code-block:: text
- DW_TAG_subprogram [3]
+ DW_TAG_subprogram [3]
DW_AT_low_pc [DW_FORM_addr] (0x0000000000000010 ".text")
DW_AT_high_pc [DW_FORM_data4] (0x00000001)
...
Index: llvm/docs/LangRef.rst
===================================================================
--- llvm/docs/LangRef.rst
+++ llvm/docs/LangRef.rst
@@ -446,7 +446,7 @@
- On iOS platforms, we use AAPCS-VFP calling convention.
"``swifttailcc``"
This calling convention is like ``swiftcc`` in most respects, but also the
- callee pops the argument area of the stack so that mandatory tail calls are
+ callee pops the argument area of the stack so that mandatory tail calls are
possible as in ``tailcc``.
"``cfguard_checkcc``" - Windows Control Flow Guard (Check mechanism)
This calling convention is used for the Control Flow Guard check function,
@@ -623,7 +623,7 @@
appropriate fencing is inserted. Since the appropriate fencing is
implementation defined, the optimizer can't do the latter. The former is
challenging as many commonly expected properties, such as
-``ptrtoint(v)-ptrtoint(v) == 0``, don't hold for non-integral types.
+``ptrtoint(v)-ptrtoint(v) == 0``, don't hold for non-integral types.
.. _globalvars:
@@ -12230,7 +12230,7 @@
declare token
@llvm.experimental.gc.statepoint(i64 <id>, i32 <num patch bytes>,
- func_type <target>,
+ func_type <target>,
i64 <#call args>, i64 <flags>,
... (call parameters),
i64 0, i64 0)
@@ -12340,7 +12340,7 @@
The first and only argument is the ``gc.statepoint`` which starts
the safepoint sequence of which this ``gc.result`` is a part.
-Despite the typing of this as a generic token, *only* the value defined
+Despite the typing of this as a generic token, *only* the value defined
by a ``gc.statepoint`` is legal here.
Semantics:
@@ -12364,8 +12364,8 @@
::
declare <pointer type>
- @llvm.experimental.gc.relocate(token %statepoint_token,
- i32 %base_offset,
+ @llvm.experimental.gc.relocate(token %statepoint_token,
+ i32 %base_offset,
i32 %pointer_offset)
Overview:
@@ -12379,7 +12379,7 @@
The first argument is the ``gc.statepoint`` which starts the
safepoint sequence of which this ``gc.relocation`` is a part.
-Despite the typing of this as a generic token, *only* the value defined
+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 the
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D113631.386365.patch
Type: text/x-patch
Size: 3593 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20211111/935ec86e/attachment.bin>
More information about the llvm-commits
mailing list