| /freebsd-14.2/contrib/llvm-project/llvm/lib/Target/AVR/ |
| H A D | AVRCallingConv.td | 8 // This describes the calling conventions for AVR architecture. 9 // Normal functions use a special calling convention, solved in code. 16 // Special return value calling convention for runtime functions. 26 // The calling conventions are implemented in custom C++ code
|
| /freebsd-14.2/contrib/one-true-awk/testdir/ |
| H A D | t.exit1 | 2 print "this is before calling myabort" 4 print "this is after calling myabort"
|
| /freebsd-14.2/crypto/openssl/doc/man3/ |
| H A D | OSSL_CALLBACK.pod | 19 the application or the calling OpenSSL libraries themselves. For example, 23 Callback functions themselves are always provided by or through the calling 33 This is a generic callback function. When calling this callback function, 41 user for a passphrase. When calling this callback function, a buffer to
|
| H A D | BIO_meth_new.pod | 83 will be called in response to the application calling BIO_write_ex() or 92 be called in response to the application calling BIO_read_ex() or BIO_read(). 101 called in response to the application calling BIO_puts(). The parameters for 107 application calling BIO_gets(). The parameters for the function have the same 113 calling BIO_ctrl(). The parameters for the function have the same meaning as for 118 called in response to the application calling BIO_new() and passing 128 called in response to the application calling BIO_free(). A pointer to the BIO 136 in response to the application calling BIO_callback_ctrl(). The parameters for
|
| H A D | OPENSSL_hexchar2int.pod | 42 The memory is allocated by calling OPENSSL_malloc() and should be 43 released by calling OPENSSL_free(). 58 The memory is allocated by calling OPENSSL_malloc() and should be 59 released by calling OPENSSL_free().
|
| H A D | SSL_CTX_get0_param.pod | 28 pointer must not be freed by the calling application. 35 are equivalent to calling X509_VERIFY_PARAM_set_purpose() directly. 39 functions are equivalent to calling X509_VERIFY_PARAM_set_trust() directly.
|
| H A D | EVP_VerifyInit.pod | 29 I<type> from ENGINE I<impl>. I<ctx> must be created by calling 30 EVP_MD_CTX_new() before calling this function. 68 be cleaned up after use by calling EVP_MD_CTX_free() or a memory leak 74 EVP_VerifyUpdate() could not be made after calling EVP_VerifyFinal().
|
| H A D | DSA_meth_new.pod | 131 called in response to the application calling DSA_do_sign() (or DSA_sign()). The 136 will be called in response to the application calling DSA_sign_setup(). The 141 response to the application calling DSA_do_verify() (or DSA_verify()). The 164 called in response to the application calling DSA_new() (if the current default 172 called in response to the application calling DSA_free(). A pointer to the DSA 179 response to the application calling DSA_generate_parameters_ex() (or 185 called in response to the application calling DSA_generate_key(). The parameter
|
| H A D | RSA_meth_new.pod | 170 called in response to the application calling RSA_sign(). The 175 function will be called in response to the application calling 194 be called in response to the application calling RSA_new() (if the 203 This function will be called in response to the application calling 211 function will be called in response to the application calling 217 respectively. This function will be called in response to the application calling 226 These functions will be called in response to the application calling
|
| H A D | SSL_CTX_set_tlsext_status_cb.pod | 49 with the returned OCSP response by calling SSL_CTX_set_tlsext_status_cb(). The 56 by calling SSL_CTX_get_tlsext_status_cb(), and the argument by calling 79 calling SSL_set_tlsext_status_ocsp_resp(). A pointer to the response data should
|
| H A D | SSL_CTX_free.pod | 30 should explicitly unset the callback by calling 31 SSL_CTX_sess_set_remove_cb(B<ctx>, NULL) prior to calling SSL_CTX_free().
|
| H A D | X509_STORE_get0_param.pod | 25 calling application 29 returned pointer must not be freed by the calling application.
|
| H A D | EVP_rc4.pod | 40 WARNING: this is not intended for usage outside of TLS and requires calling of 49 calling these functions multiple times and should consider using
|
| H A D | SSL_write.pod | 24 Kernel TLS is enabled, which can be checked by calling BIO_get_ktls_send(). 41 initialized to client or server mode. This is being done by calling 53 call to a write function can also cause read operations! The calling process 107 closed, an error occurred or action must be taken by the calling process. 129 closed, an error occurred or action must be taken by the calling process.
|
| H A D | DH_meth_new.pod | 102 be called in response to the application calling DH_generate_key(). The 107 will be called in response to the application calling DH_compute_key(). The 122 called in response to the application calling DH_new() (if the current default 130 called in response to the application calling DH_free(). A pointer to the DH 137 called in response to the application calling DH_generate_parameters_ex() (or
|
| /freebsd-14.2/contrib/llvm-project/llvm/lib/Target/PowerPC/ |
| H A D | PPCCallingConv.td | 9 // This describes the calling conventions for the PowerPC 32- and 64-bit 40 // This calling convention is currently only supported by the stackmap and 42 // builds. On Release builds we fallback to the PPC C calling convention. 105 // No explicit register is specified for the AnyReg calling convention. The 108 // This calling convention is currently only supported by the stackmap and 110 // builds. On Release builds we fallback to the PPC C calling convention. 116 // This calling convention currently only handles integers, floats and 156 // Simple calling convention for 64-bit ELF PowerPC fast isel. 278 // Helper "calling convention" to handle aggregate by value arguments. 286 // the CC_PPC32_SVR4 calling convention. [all …]
|
| /freebsd-14.2/crypto/openssl/doc/man7/ |
| H A D | EVP_KDF-TLS13_KDF.pod | 63 In this mode calling L<EVP_KDF_derive(3)> will just perform the extract 66 up by calling EVP_KDF_CTX_get_kdf_size() after setting the mode and digest. 73 In this mode calling L<EVP_KDF_derive(3)> will just perform the expand 93 A context for a TLS 1.3 KDF can be obtained by calling: 102 For that mode, the fixed output size can be looked up by calling
|
| H A D | EVP_KDF-HKDF.pod | 66 In this mode calling L<EVP_KDF_derive(3)> will just perform the extract 69 up by calling EVP_KDF_CTX_get_kdf_size() after setting the mode and digest. 76 In this mode calling L<EVP_KDF_derive(3)> will just perform the expand 89 A context for HKDF can be obtained by calling: 98 For that mode, the fixed output size can be looked up by calling EVP_KDF_CTX_get_kdf_size()
|
| H A D | EVP_PKEY-SM2.pod | 40 Ditto for the verification process by calling the 'DigestVerify' series of APIs. 50 Before calling the EVP_DigestSignInit() or EVP_DigestVerifyInit() functions, 66 This example demonstrates the calling sequence for using an B<EVP_PKEY> to verify
|
| H A D | EVP_PKEY-DSA.pod | 50 An B<EVP_PKEY> context can be obtained by calling: 54 The B<DSA> domain parameters can be generated by calling: 78 A B<DSA> key can be generated using domain parameters by calling:
|
| H A D | X25519.pod | 22 A context for the B<X25519> algorithm can be obtained by calling: 26 For the B<X448> algorithm a context can be obtained by calling:
|
| /freebsd-14.2/contrib/llvm-project/llvm/include/llvm/Target/ |
| H A D | TargetCallingConv.td | 10 // describe their calling conventions. 74 /// CCIfCC - Match if the current calling convention is 'CC'. 191 /// CCDelegateTo - This action invokes the specified sub-calling-convention. It 197 /// CallingConv - An instance of this is used to define each calling convention 202 /// If true, this calling convention will be emitted as externally visible in 209 /// CustomCallingConv - An instance of this is used to declare calling 215 /// CalleeSavedRegs - A list of callee saved registers for a given calling
|
| /freebsd-14.2/contrib/llvm-project/llvm/lib/Target/SystemZ/ |
| H A D | SystemZCallingConv.td | 8 // This describes the calling conventions for the SystemZ ABI. 33 // z/Linux return value calling convention 65 // z/Linux argument calling conventions for GHC 88 // z/Linux argument calling conventions 153 // "All registers" as used by the AnyReg calling convention. 173 // z/OS XPLINK64 return value calling convention 204 // z/OS XPLINK64 argument calling conventions 287 // s390x return value calling convention 300 // s390x argument calling conventions
|
| /freebsd-14.2/contrib/llvm-project/llvm/lib/Target/RISCV/ |
| H A D | RISCVCallingConv.td | 9 // This describes the calling conventions for the RISC-V architecture. 13 // The RISC-V calling convention is handled with custom code in
|
| /freebsd-14.2/contrib/llvm-project/llvm/lib/Target/X86/ |
| H A D | X86CallingConv.td | 9 // This describes the calling conventions for the X86-32 and X86-64 112 // X86-64 Intel regcall calling convention. 302 // weirdly; this is really the sse-regparm calling convention) in which 329 // Otherwise, it is the same as the common X86 calling convention. 373 // The X86-64 calling convention always returns FP values in XMM0. 392 // The X86-Win64 calling convention always returns __m64 values in RAX. 405 // Vectorcall calling convention always returns FP values in XMMs. 522 // Check if this is the Intel OpenCL built-ins calling convention 690 // Do not pass the sret argument in RCX, the Win64 thiscall calling 1028 // X86-64 Intel OpenCL built-ins calling convention. [all …]
|