Searched refs:increment (Results 1 – 19 of 19) sorted by relevance
| /openssl-master/providers/implementations/digests/ |
| A D | blake2b_prov.c | 161 size_t increment; in blake2b_compress() local
182 increment = len < BLAKE2B_BLOCKBYTES ? len : BLAKE2B_BLOCKBYTES; in blake2b_compress()
194 S->t[0] += increment; in blake2b_compress()
195 S->t[1] += (S->t[0] < increment); in blake2b_compress()
252 blocks += increment; in blake2b_compress()
253 len -= increment; in blake2b_compress()
|
| A D | blake2s_prov.c | 154 size_t increment; in blake2s_compress() local
175 increment = len < BLAKE2S_BLOCKBYTES ? len : BLAKE2S_BLOCKBYTES; in blake2s_compress()
187 S->t[0] += increment; in blake2s_compress()
188 S->t[1] += (S->t[0] < increment); in blake2s_compress()
243 blocks += increment; in blake2s_compress()
244 len -= increment; in blake2s_compress()
|
| /openssl-master/doc/man3/ |
| A D | SSL_CTX_set_cert_store.pod | 50 SSL_CTX_set_cert_store() does not increment the B<store>'s reference
57 increment the reference count of the X509_STORE.
|
| A D | SSL_CTX_set1_verify_cert_store.pod | 38 increment the reference count of the supplied store so it must
40 not increment reference counts and the supplied store B<MUST NOT> be freed
|
| A D | X509_get_pubkey.pod | 29 after use. X509_get0_pubkey() is similar except it does B<not> increment
|
| A D | SSL_CTX_add1_chain_cert.pod | 98 increment the reference count of the supplied certificate or chain so it must
100 not increment reference counts and the supplied certificate or chain
|
| A D | SSL_set_bio.pod | 29 ownership of one reference. Therefore, it may be necessary to increment the
|
| A D | SSL_get_session.pod | 70 If the data is to be kept, SSL_get1_session() will increment the reference
|
| A D | SSL_CTX_sess_set_get_cb.pod | 95 SSL engine to increment the reference count of the SSL_SESSION object;
|
| A D | ASN1_EXTERN_FUNCS.pod | 119 the buffer in I<*out>, and then increment I<*out> to point to immediately after
|
| A D | d2i_RSAPrivateKey.pod | 270 The reason for this-auto increment behaviour is to reflect a typical
|
| A D | d2i_X509.pod | 439 The reason for this-auto increment behaviour is to reflect a typical
|
| A D | X509_STORE_CTX_get_error.pod | 63 needs to increment its reference count via L<X509_up_ref(3)>.
|
| A D | X509_VERIFY_PARAM_set_flags.pod | 138 To obtain all names start with B<n> = 0 and increment B<n> as long as no NULL
|
| /openssl-master/doc/internal/man3/ |
| A D | OSSL_METHOD_STORE.pod | 71 If the I<method_up_ref> function is given, it's called to increment the
101 The I<method_up_ref> function is called to increment the
|
| A D | ossl_method_construct.pod | 101 This function is expected to increment the resulting method's reference count.
118 This function is expected to increment the I<method>'s reference count.
|
| /openssl-master/crypto/aes/asm/ |
| A D | aesni-x86_64.pl | 983 my $increment="%xmm9";
1000 movaps %xmm9,0x30(%rsp) # $increment
1006 movdqa .Lincrement64(%rip),$increment
1041 paddq $increment,$iv
1093 movaps %xmm9,0x30(%rsp) # $increment
1100 movdqa .Lincrement64(%rip),$increment
1113 paddq $increment,$iv
1149 paddq $increment,$iv
|
| /openssl-master/crypto/engine/ |
| A D | README.md | 155 (ie. it's simply an increment of the functional reference count, and no real
|
| /openssl-master/ |
| A D | CHANGES.md | 12381 * Give DH, DSA, and RSA types their own `*_up_ref()` function to increment
15099 In BIO_puts, increment b->num_write as in BIO_write.
15834 (Some of the existing 'get' functions increment a reference
|
Completed in 46 milliseconds