[llvm] 9fc4654 - [LangRef] Fix mislabeling in calling convention name (NFC)

[Antonio Frighetto via llvm-commits]

Author: Antonio Frighetto
Date: 2024-11-18T11:02:10+01:00
New Revision: 9fc4654462c44569bab950c18d25ca7624f10691

URL: https://github.com/llvm/llvm-project/commit/9fc4654462c44569bab950c18d25ca7624f10691
DIFF: https://github.com/llvm/llvm-project/commit/9fc4654462c44569bab950c18d25ca7624f10691.diff

LOG: [LangRef] Fix mislabeling in calling convention name (NFC)

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.

Added: 
    

Modified: 
    llvm/docs/LangRef.rst

Removed: 
    


################################################################################
diff  --git a/llvm/docs/LangRef.rst b/llvm/docs/LangRef.rst
index 99f3ec20e1dad3..9f4c90ba82a419 100644
--- a/llvm/docs/LangRef.rst
+++ b/llvm/docs/LangRef.rst
@@ -12836,7 +12836,7 @@ This instruction requires several arguments:
    - The caller and callee prototypes must match. Pointer types of parameters
      or return types may 
diff er 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.