[llvm] [LangRef] Add a description of the semantics of call signatures. (PR #136189)

Nikita Popov via llvm-commits llvm-commits at lists.llvm.org
Thu Apr 17 13:10:10 PDT 2025


================
@@ -9475,10 +9475,11 @@ This instruction requires several arguments:
    from the :ref:`datalayout string<langref_datalayout>` will be used.
 #. '``ty``': the type of the call instruction itself which is also the
    type of the return value. Functions that return no value are marked
-   ``void``.
+   ``void``. The signature is computed based on the return type and argument
+   types.
 #. '``fnty``': shall be the signature of the function being invoked. The
-   argument types must match the types implied by this signature. This
-   type can be omitted if the function is not varargs.
+   argument types must match the types implied by this signature. Thisa
----------------
nikic wrote:

```suggestion
   argument types must match the types implied by this signature. This
```

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


More information about the llvm-commits mailing list