Skip to content

Commit 24684c1

Browse files
committed
Fix link
1 parent 5809664 commit 24684c1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

llvm/docs/LangRef.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16734,7 +16734,7 @@ so arithmetic feeding into a minnum can produce inconsistent results. For exampl
1673416734
``minnum(fadd(sNaN, -0.0), 1.0)`` can produce qNaN or 1.0 depending on whether ``fadd`` is folded.
1673516735

1673616736
IEEE-754-2008 defines minNum, and it was removed in IEEE-754-2019. As the replacement, IEEE-754-2019
16737-
defines :ref:`minimumNumber <llvm-minimumnum-intrinsic>`.
16737+
defines :ref:`minimumNumber <i_minimumnum>`.
1673816738

1673916739
If the intrinsic is marked with the nsz attribute, then the effect is as in the definition in C
1674016740
and IEEE-754-2008: the result of ``minnum(-0.0, +0.0)`` may be either -0.0 or +0.0.
@@ -16794,7 +16794,7 @@ so arithmetic feeding into a maxnum can produce inconsistent results. For exampl
1679416794
``maxnum(fadd(sNaN, -0.0), 1.0)`` can produce qNaN or 1.0 depending on whether ``fadd`` is folded.
1679516795

1679616796
IEEE-754-2008 defines maxNum, and it was removed in IEEE-754-2019. As the replacement, IEEE-754-2019
16797-
defines :ref:`maximumNumber <llvm-maximumnum-intrinsic>`.
16797+
defines :ref:`maximumNumber <i_maximumnum>`.
1679816798

1679916799
If the intrinsic is marked with the nsz attribute, then the effect is as in the definition in C
1680016800
and IEEE-754-2008: the result of maxnum(-0.0, +0.0) may be either -0.0 or +0.0.

0 commit comments

Comments
 (0)