[llvm] [LangRef] Fix mislabeling in calling convention name (NFC) (PR #111256)

[via llvm-commits]

llvmbot wrote:


<!--LLVM PR SUMMARY COMMENT-->

@llvm/pr-subscribers-llvm-ir

Author: Antonio Frighetto (antoniofrighetto)

<details>
<summary>Changes</summary>

We have explained how musttail can be guaranteed when the calling convention is not `swifttailcc` or `tailcc`, ensure what needs to adhere when it is the opposite case (reflect how it is already handled in Verifier).

---
Full diff: https://github.com/llvm/llvm-project/pull/111256.diff


1 Files Affected:

- (modified) llvm/docs/LangRef.rst (+1-1) 


``````````diff
diff --git a/llvm/docs/LangRef.rst b/llvm/docs/LangRef.rst
index 6fa35486669d69..1dd4279efcfb68 100644
--- a/llvm/docs/LangRef.rst
+++ b/llvm/docs/LangRef.rst
@@ -12747,7 +12747,7 @@ This instruction requires several arguments:
    - The caller and callee prototypes must match. Pointer types of parameters
      or return types may differ in pointee type, but not in address space.
 
-  On the other hand, if the calling convention is `swifttailcc` or `swiftcc`:
+  On the other hand, if the calling convention is `swifttailcc` or `tailcc`:
 
    - Only these ABI-impacting attributes attributes are allowed: sret, byval,
      swiftself, and swiftasync.

``````````

</details>


https://github.com/llvm/llvm-project/pull/111256