Searched refs:calling (Results 1 – 25 of 490) sorted by relevance
12345678910>>...20
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.27 // The calling conventions are implemented in custom C++ code
21 Ditto for the verification process by calling the 'DigestVerify' series of APIs.27 created. It should be set to B<EVP_PKEY_SM2> by calling:31 Then an ID should be set by calling:35 When calling the EVP_DigestSignInit() or EVP_DigestVerifyInit() functions, a37 done by calling:46 This example demonstrates the calling sequence for using an B<EVP_PKEY> to verify
27 When calling EVP_DigestSignInit() or EVP_DigestVerifyInit(), the34 A context for the B<Ed25519> algorithm can be obtained by calling:38 For the B<Ed448> algorithm a context can be obtained by calling:
162 if(IE_ISGOOD(src->calling)) in copy_msg_setup()163 dst->calling = src->calling; in copy_msg_setup()295 if(IE_ISGOOD(src->calling)) in copy_msg_add_party()296 dst->calling = src->calling; in copy_msg_add_party()445 if(IE_ISGOOD(src->calling)) in copy_msg_leaf_setup_req()446 dst->calling = src->calling; in copy_msg_leaf_setup_req()492 if(IE_ISGOOD(src->calling)) in copy_msg_cobisetup()493 dst->calling = src->calling; in copy_msg_cobisetup()509 if(IE_ISGOOD(src->calling)) in copy_msg_facility()510 dst->calling = src->calling; in copy_msg_facility()
9 // This describes the calling conventions for the PowerPC 32- and 64-bit40 // This calling convention is currently only supported by the stackmap and42 // builds. On Release builds we fallback to the PPC C calling convention.105 // No explicit register is specified for the AnyReg calling convention. The108 // This calling convention is currently only supported by the stackmap and110 // builds. On Release builds we fallback to the PPC C calling convention.115 // Note that we don't currently have calling conventions for 64-bit120 // Simple calling convention for 64-bit ELF PowerPC fast isel.222 // This calling convention puts vector arguments always on the stack. It is used230 // In contrast to CC_PPC32_SVR4_VarArg, this calling convention first tries to[all …]
83 will be called in response to the application calling BIO_write_ex() or92 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 for107 application calling BIO_gets(). The parameters for the function have the same113 calling BIO_ctrl(). The parameters for the function have the same meaning as for118 called in response to the application calling BIO_new() and passing125 called in response to the application calling BIO_free(). A pointer to the BIO133 in response to the application calling BIO_callback_ctrl(). The parameters for
26 B<type> from ENGINE B<impl>. B<ctx> must be created by calling27 EVP_MD_CTX_new() before calling this function.60 be cleaned up after use by calling EVP_MD_CTX_free() or a memory leak66 EVP_VerifyUpdate() could not be made after calling EVP_VerifyFinal().
124 called in response to the application calling DSA_do_sign() (or DSA_sign()). The129 will be called in response to the application calling DSA_sign_setup(). The134 response to the application calling DSA_do_verify() (or DSA_verify()). The157 called in response to the application calling DSA_new() (if the current default165 called in response to the application calling DSA_free(). A pointer to the DSA172 response to the application calling DSA_generate_parameters_ex() (or178 called in response to the application calling DSA_generate_key(). The parameter
164 called in response to the application calling RSA_sign(). The169 function will be called in response to the application calling188 be called in response to the application calling RSA_new() (if the197 This function will be called in response to the application calling205 function will be called in response to the application calling211 respectively. This function will be called in response to the application calling220 These functions will be called in response to the application calling
23 calling application27 returned pointer must not be freed by the calling application.
49 with the returned OCSP response by calling SSL_CTX_set_tlsext_status_cb(). The56 by calling SSL_CTX_get_tlsext_status_cb(), and the argument by calling79 calling SSL_set_tlsext_status_ocsp_resp(). A pointer to the response data should
95 be called in response to the application calling DH_generate_key(). The100 will be called in response to the application calling DH_compute_key(). The115 called in response to the application calling DH_new() (if the current default123 called in response to the application calling DH_free(). A pointer to the DH130 called in response to the application calling DH_generate_parameters_ex() (or
53 If the B<*a> is not NULL when calling d2i_PrivateKey() or d2i_AutoPrivateKey()65 error occurs. The error code can be obtained by calling L<ERR_get_error(3)>.69 by calling L<ERR_get_error(3)>.
102 The old buffer is filled with zero's by calling OPENSSL_cleanse()103 before ultimately calling OPENSSL_free().114 equivalent C functions, except that memory is allocated by calling the115 OPENSSL_malloc() and should be released by calling OPENSSL_free().122 pointer to the parsed value. The memory is allocated by calling123 OPENSSL_malloc() and should be released by calling OPENSSL_free().167 At the end of the program, calling CRYPTO_mem_leaks() or
30 should explicitly unset the callback by calling31 SSL_CTX_sess_set_remove_cb(B<ctx>, NULL) prior to calling SSL_CTX_free().
86 struct uni_ie_calling calling; member158 struct uni_ie_calling calling; member231 struct uni_ie_calling calling; member255 struct uni_ie_calling calling; member265 struct uni_ie_calling calling; member
195 calling316 calling446 calling486 calling504 calling
10 // describe their calling conventions.74 /// CCIfCC - Match if the current calling convention is 'CC'.182 /// CCDelegateTo - This action invokes the specified sub-calling-convention. It188 /// CallingConv - An instance of this is used to define each calling convention193 /// If true, this calling convention will be emitted as externally visible in200 /// CustomCallingConv - An instance of this is used to declare calling206 /// CalleeSavedRegs - A list of callee saved registers for a given calling
8 // This describes the calling conventions for the SystemZ ABI.33 // z/Linux return value calling convention65 // z/Linux argument calling conventions for GHC88 // z/Linux argument calling conventions152 // "All registers" as used by the AnyReg calling convention.173 // z/OS XPLINK64 return value calling convention204 // z/OS XPLINK64 argument calling conventions289 // s390x return value calling convention302 // s390x argument calling conventions
9 // This describes the calling conventions for the X86-32 and X86-6474 // X86-64 Intel regcall calling convention.262 // The X86-32 calling convention returns FP values in FP0, unless marked264 // weirdly; this is really the sse-regparm calling convention) in which265 // case they use XMM0, otherwise it is the same as the common X86 calling287 // Otherwise, it is the same as the common X86 calling convention.331 // The X86-64 calling convention always returns FP values in XMM0.349 // The X86-Win64 calling convention always returns __m64 values in RAX.362 // Vectorcall calling convention always returns FP values in XMMs.414 // This calling convention is currently only supported by the stackmap and[all …]
43 * the dynamic APR-UTIL library and assure appropriate indirection and calling49 * use the most appropriate calling convention. Public APR functions with 57 * APU_DECLARE_NONSTD(), as they must use the C language calling convention.
41 * the dynamic APR-UTIL library and assure appropriate indirection and calling48 * use the most appropriate calling convention. Public APR functions with 56 * APU_DECLARE_NONSTD(), as they must use the C language calling convention.
41 * the dynamic APR-UTIL library and assure appropriate indirection and calling54 * use the most appropriate calling convention. Public APR functions with 62 * APU_DECLARE_NONSTD(), as they must use the C language calling convention.
9 // This describes the calling conventions for the RISCV architecture.13 // The RISC-V calling convention is handled with custom code in