Skip to content

Commit 689f19b

Browse files
Revert whitespace changes in LangRef.rst
1 parent 04c350b commit 689f19b

File tree

1 file changed

+17
-17
lines changed

1 file changed

+17
-17
lines changed

llvm/docs/LangRef.rst

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -354,7 +354,7 @@ added in the future:
354354
not be used lightly but only for specific situations such as an
355355
alternative to the *register pinning* performance technique often
356356
used when implementing functional programming languages. At the
357-
moment only X86, AArch64, and RISCV support this convention. The
357+
moment only X86, AArch64, and RISCV support this convention. The
358358
following limitations exist:
359359

360360
- On *X86-32* only up to 4 bit type parameters are supported. No
@@ -685,10 +685,10 @@ implementation defined, the optimizer can't do the latter. The former is
685685
challenging as many commonly expected properties, such as
686686
``ptrtoint(v)-ptrtoint(v) == 0``, don't hold for non-integral types.
687687
Similar restrictions apply to intrinsics that might examine the pointer bits,
688-
such as :ref:`llvm.ptrmask<int_ptrmask>`.
688+
such as :ref:`llvm.ptrmask<int_ptrmask>`.
689689

690690
The alignment information provided by the frontend for a non-integral pointer
691-
(typically using attributes or metadata) must be valid for every possible
691+
(typically using attributes or metadata) must be valid for every possible
692692
representation of the pointer.
693693

694694
.. _globalvars:
@@ -1677,10 +1677,10 @@ Currently, only the following parameter attributes are defined:
16771677
- The range is allowed to wrap.
16781678
- The empty range is represented using ``0,0``.
16791679
- Otherwise, ``a`` and ``b`` are not allowed to be equal.
1680-
1681-
This attribute may only be applied to parameters or return values with integer
1680+
1681+
This attribute may only be applied to parameters or return values with integer
16821682
or vector of integer types.
1683-
1683+
16841684
For vector-typed parameters, the range is applied element-wise.
16851685

16861686
.. _gc:
@@ -14347,7 +14347,7 @@ Arguments:
1434714347
""""""""""
1434814348
The first 4 arguments are similar to ``llvm.instrprof.increment``. The indexing
1434914349
is specific to callsites, meaning callsites are indexed from 0, independent from
14350-
the indexes used by the other intrinsics (such as
14350+
the indexes used by the other intrinsics (such as
1435114351
``llvm.instrprof.increment[.step]``).
1435214352

1435314353
The last argument is the called value of the callsite this intrinsic precedes.
@@ -14361,7 +14361,7 @@ a buffer LLVM can use to perform counter increments (i.e. the lowering of
1436114361
``llvm.instrprof.increment[.step]``. The address range following the counter
1436214362
buffer, ``<num-counters>`` x ``sizeof(ptr)`` - sized, is expected to contain
1436314363
pointers to contexts of functions called from this function ("subcontexts").
14364-
LLVM does not dereference into that memory region, just calculates GEPs.
14364+
LLVM does not dereference into that memory region, just calculates GEPs.
1436514365

1436614366
The lowering of ``llvm.instrprof.callsite`` consists of:
1436714367

@@ -14930,8 +14930,8 @@ integer bit width or any vector of integer elements.
1493014930
Overview:
1493114931
"""""""""
1493214932

14933-
Return ``-1`` if ``%a`` is signed less than ``%b``, ``0`` if they are equal, and
14934-
``1`` if ``%a`` is signed greater than ``%b``. Vector intrinsics operate on a per-element basis.
14933+
Return ``-1`` if ``%a`` is signed less than ``%b``, ``0`` if they are equal, and
14934+
``1`` if ``%a`` is signed greater than ``%b``. Vector intrinsics operate on a per-element basis.
1493514935

1493614936
Arguments:
1493714937
""""""""""
@@ -14959,8 +14959,8 @@ integer bit width or any vector of integer elements.
1495914959
Overview:
1496014960
"""""""""
1496114961

14962-
Return ``-1`` if ``%a`` is unsigned less than ``%b``, ``0`` if they are equal, and
14963-
``1`` if ``%a`` is unsigned greater than ``%b``. Vector intrinsics operate on a per-element basis.
14962+
Return ``-1`` if ``%a`` is unsigned less than ``%b``, ``0`` if they are equal, and
14963+
``1`` if ``%a`` is unsigned greater than ``%b``. Vector intrinsics operate on a per-element basis.
1496414964

1496514965
Arguments:
1496614966
""""""""""
@@ -21557,9 +21557,9 @@ Semantics:
2155721557
""""""""""
2155821558

2155921559
The '``llvm.vp.minimum``' intrinsic performs floating-point minimum (:ref:`minimum <i_minimum>`)
21560-
of the first and second vector arguments on each enabled lane, the result being
21560+
of the first and second vector arguments on each enabled lane, the result being
2156121561
NaN if either argument is a NaN. -0.0 is considered to be less than +0.0 for this
21562-
intrinsic. The result on disabled lanes is a :ref:`poison value <poisonvalues>`.
21562+
intrinsic. The result on disabled lanes is a :ref:`poison value <poisonvalues>`.
2156321563
The operation is performed in the default floating-point environment.
2156421564

2156521565
Examples:
@@ -29192,7 +29192,7 @@ Semantics:
2919229192
""""""""""
2919329193

2919429194
The intrinsic ``@llvm.allow.ubsan.check()`` returns either ``true`` or
29195-
``false``, depending on compiler options.
29195+
``false``, depending on compiler options.
2919629196

2919729197
For each evaluation of a call to this intrinsic, the program must be valid and
2919829198
correct both if it returns ``true`` and if it returns ``false``.
@@ -29251,13 +29251,13 @@ Semantics:
2925129251
""""""""""
2925229252

2925329253
The intrinsic ``@llvm.allow.runtime.check()`` returns either ``true`` or
29254-
``false``, depending on compiler options.
29254+
``false``, depending on compiler options.
2925529255

2925629256
For each evaluation of a call to this intrinsic, the program must be valid and
2925729257
correct both if it returns ``true`` and if it returns ``false``.
2925829258

2925929259
When used in a branch condition, it allows us to choose between
29260-
two alternative correct solutions for the same problem.
29260+
two alternative correct solutions for the same problem.
2926129261

2926229262
If the intrinsic is evaluated as ``true``, program should execute a guarded
2926329263
check. If the intrinsic is evaluated as ``false``, the program should avoid any

0 commit comments

Comments
 (0)