Home
last modified time | relevance | path

Searched refs:calling (Results 1 – 25 of 1636) sorted by relevance

12345678910>>...66

/netbsd-src/crypto/external/bsd/openssl.old/dist/doc/man7/
H A DSM2.pod21 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, a
37 done by calling:
46 This example demonstrates the calling sequence for using an B<EVP_PKEY> to verify
H A DEd25519.pod27 When calling EVP_DigestSignInit() or EVP_DigestVerifyInit(), the
34 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:
/netbsd-src/external/apache2/llvm/dist/llvm/lib/Target/AVR/
H A DAVRCallingConv.td8 // 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
/netbsd-src/external/apache2/llvm/dist/llvm/lib/Target/PowerPC/
H A DPPCCallingConv.td9 // 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.
115 // Note that we don't currently have calling conventions for 64-bit
120 // Simple calling convention for 64-bit ELF PowerPC fast isel.
222 // This calling convention puts vector arguments always on the stack. It is used
230 // In contrast to CC_PPC32_SVR4_VarArg, this calling convention first tries to
[all …]
/netbsd-src/crypto/external/bsd/openssl.old/dist/doc/man3/
H A DBIO_meth_new.pod83 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
125 called in response to the application calling BIO_free(). A pointer to the BIO
133 in response to the application calling BIO_callback_ctrl(). The parameters for
H A DEVP_VerifyInit.pod26 B<type> from ENGINE B<impl>. B<ctx> must be created by calling
27 EVP_MD_CTX_new() before calling this function.
60 be cleaned up after use by calling EVP_MD_CTX_free() or a memory leak
66 EVP_VerifyUpdate() could not be made after calling EVP_VerifyFinal().
H A DDSA_meth_new.pod124 called in response to the application calling DSA_do_sign() (or DSA_sign()). The
129 will be called in response to the application calling DSA_sign_setup(). The
134 response to the application calling DSA_do_verify() (or DSA_verify()). The
157 called in response to the application calling DSA_new() (if the current default
165 called in response to the application calling DSA_free(). A pointer to the DSA
172 response to the application calling DSA_generate_parameters_ex() (or
178 called in response to the application calling DSA_generate_key(). The parameter
H A DRSA_meth_new.pod164 called in response to the application calling RSA_sign(). The
169 function will be called in response to the application calling
188 be called in response to the application calling RSA_new() (if the
197 This function will be called in response to the application calling
205 function will be called in response to the application calling
211 respectively. This function will be called in response to the application calling
220 These functions will be called in response to the application calling
H A DSSL_CTX_set_tlsext_status_cb.pod49 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 DDH_meth_new.pod95 be called in response to the application calling DH_generate_key(). The
100 will be called in response to the application calling DH_compute_key(). The
115 called in response to the application calling DH_new() (if the current default
123 called in response to the application calling DH_free(). A pointer to the DH
130 called in response to the application calling DH_generate_parameters_ex() (or
H A DX509_STORE_get0_param.pod23 calling application
27 returned pointer must not be freed by the calling application.
H A DOPENSSL_malloc.pod102 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 the
115 OPENSSL_malloc() and should be released by calling OPENSSL_free().
122 pointer to the parsed value. The memory is allocated by calling
123 OPENSSL_malloc() and should be released by calling OPENSSL_free().
167 At the end of the program, calling CRYPTO_mem_leaks() or
/netbsd-src/crypto/external/bsd/openssl/dist/doc/man3/
H A DOSSL_CALLBACK.pod19 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 DOPENSSL_hexchar2int.pod42 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 DSSL_CTX_get0_param.pod28 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 DEVP_VerifyInit.pod29 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 DSSL_CTX_set_tlsext_status_cb.pod49 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
/netbsd-src/crypto/external/bsd/openssl/dist/doc/man7/
H A DEVP_KDF-TLS13_KDF.pod61 In this mode calling L<EVP_KDF_derive(3)> will just perform the extract
64 up by calling EVP_KDF_CTX_get_kdf_size() after setting the mode and digest.
71 In this mode calling L<EVP_KDF_derive(3)> will just perform the expand
91 A context for a TLS 1.3 KDF can be obtained by calling:
100 For that mode, the fixed output size can be looked up by calling
H A DEVP_KDF-HKDF.pod64 In this mode calling L<EVP_KDF_derive(3)> will just perform the extract
67 up by calling EVP_KDF_CTX_get_kdf_size() after setting the mode and digest.
74 In this mode calling L<EVP_KDF_derive(3)> will just perform the expand
87 A context for HKDF can be obtained by calling:
96 For that mode, the fixed output size can be looked up by calling EVP_KDF_CTX_get_kdf_size()
H A DEVP_PKEY-SM2.pod40 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
/netbsd-src/external/historical/nawk/dist/testdir/
H A Dt.exit12 print "this is before calling myabort"
4 print "this is after calling myabort"
/netbsd-src/external/apache2/llvm/dist/llvm/include/llvm/Target/
H A DTargetCallingConv.td10 // describe their calling conventions.
74 /// CCIfCC - Match if the current calling convention is 'CC'.
182 /// CCDelegateTo - This action invokes the specified sub-calling-convention. It
188 /// CallingConv - An instance of this is used to define each calling convention
193 /// If true, this calling convention will be emitted as externally visible in
200 /// CustomCallingConv - An instance of this is used to declare calling
206 /// CalleeSavedRegs - A list of callee saved registers for a given calling
/netbsd-src/external/apache2/llvm/dist/llvm/lib/Target/SystemZ/
H A DSystemZCallingConv.td8 // 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
152 // "All registers" as used by the AnyReg calling convention.
173 // z/OS XPLINK64 return value calling convention
204 // z/OS XPLINK64 argument calling conventions
289 // s390x return value calling convention
302 // s390x argument calling conventions
/netbsd-src/external/gpl3/gcc.old/dist/gcc/d/
H A Druntime.def51 /* Used when calling new on a class. */
54 /* Used when calling delete on a class or interface. */
69 /* Used when calling new on a pointer. The `i' variant is for when the
74 /* Used when calling delete on a pointer. */
79 /* Used when calling new on an array. The `i' variant is for when the
95 /* Used when calling delete on an array. */
187 /* Used when calling delete on a key entry in an associative array. */
/netbsd-src/external/apache2/llvm/dist/llvm/lib/Target/X86/
H A DX86CallingConv.td9 // This describes the calling conventions for the X86-32 and X86-64
74 // X86-64 Intel regcall calling convention.
262 // The X86-32 calling convention returns FP values in FP0, unless marked
264 // weirdly; this is really the sse-regparm calling convention) in which
265 // case they use XMM0, otherwise it is the same as the common X86 calling
287 // 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 …]

12345678910>>...66