[llvm] [LangRef] Fix language around strictfp semantics (PR #213879)

[Ramkumar Ramachandra via llvm-commits]

https://github.com/artagnon updated https://github.com/llvm/llvm-project/pull/213879

>From 7b7eb12fe7e36089b67f4b17f1c66558b0857219 Mon Sep 17 00:00:00 2001
From: Ramkumar Ramachandra <artagnon at tenstorrent.com>
Date: Tue, 4 Aug 2026 10:07:34 +0100
Subject: [PATCH] [LangRef] Fix language around strictfp semantics
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The LangRef wording changed in 15bb4a97a7 ([IR] Make semantics of
strictfp consistent v2, #211769) is unfortunately unclear and incorrect.
Clarify what was intended.

Reported-by: Ömer Sinan Ağacan <omer at osa1.net>
---
 llvm/docs/LangRef.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/llvm/docs/LangRef.md b/llvm/docs/LangRef.md
index 1fc6ea1a7ed9d..843a2d626cd06 100644
--- a/llvm/docs/LangRef.md
+++ b/llvm/docs/LangRef.md
@@ -2800,8 +2800,7 @@ fn -> other_fn -> other_fn ; fn is norecurse
     optimizations that require assumptions about the floating-point rounding
     mode or that might alter the state of floating-point status flags that
     might otherwise be set or cleared by calling this function. LLVM will
-    not introduce any new floating-point instructions that may trap. All
-    function definitions that contain strictfp calls must be marked strictfp.
+    not introduce any new floating-point instructions that may trap.
 
 (denormal_fpenv)=
 
@@ -26741,6 +26740,9 @@ point intrinsics must have the `strictfp` attribute either on the
 calling instruction or on the declaration or definition of the function
 being called.
 
+All function *definitions* that use constrained floating point intrinsics
+must have the `strictfp` attribute.
+
 #### '`llvm.experimental.constrained.fadd`' Intrinsic
 
 ##### Syntax: