[llvm] [AMDGPU] Drop docs for invalid load-release and store-acquire operations (PR #202338)

[via llvm-commits]

https://github.com/graphite-app[bot] updated https://github.com/llvm/llvm-project/pull/202338

>From eb954b0bb91f3a9374a00279650e1a0977871062 Mon Sep 17 00:00:00 2001
From: ritter-x2a <9519134+ritter-x2a at users.noreply.github.com>
Date: Tue, 9 Jun 2026 06:58:59 +0000
Subject: [PATCH] [AMDGPU] Drop docs for invalid load-release and store-acquire
 operations (#202338)

The LangRef says "release and acq_rel orderings are not valid on load
instructions" [for loads](https://llvm.org/docs/LangRef.html#load-instruction)
and "acquire and acq_rel orderings aren't valid on store instructions"
[for stores](https://llvm.org/docs/LangRef.html#store-instruction).
Providing them in textual IR is diagnosed with an error.

Therefore, we should not define semantics for these invalid constructs.

Part of LCOMPILER-2273.
---
 llvm/docs/AMDGPUUsage.rst | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/llvm/docs/AMDGPUUsage.rst b/llvm/docs/AMDGPUUsage.rst
index 121b66a657f5d..ed4c759fd24f8 100644
--- a/llvm/docs/AMDGPUUsage.rst
+++ b/llvm/docs/AMDGPUUsage.rst
@@ -7214,15 +7214,6 @@ orderings (``acquire``, ``release``, ``acq_rel``, or ``seq_cst``).
 The memory model does not support the region address space which is treated as
 non-atomic.
 
-Acquire memory ordering is not meaningful on store atomic instructions and is
-treated as non-atomic.
-
-Release memory ordering is not meaningful on load atomic instructions and is
-treated as non-atomic.
-
-Acquire-release memory ordering is not meaningful on load or store atomic
-instructions and is treated as acquire and release respectively.
-
 The memory order also adds the single thread optimization constraints defined in
 table
 :ref:`amdgpu-amdhsa-memory-model-single-thread-optimization-constraints-table`.