Home
last modified time | relevance | path

Searched refs:future (Results 1 – 25 of 423) sorted by relevance

12345678910>>...17

/src/contrib/llvm-project/libcxx/include/
H A Dfuture14 future synopsis
75 future<R> get_future();
105 future<R&> get_future();
133 future<void> get_future();
150 class future
153 future() noexcept;
154 future(future&&) noexcept;
155 future(const future& rhs) = delete;
156 ~future();
157 future& operator=(const future& rhs) = delete;
[all …]
/src/contrib/llvm-project/libcxx/src/
H A Dfuture.cpp127 future<void>::future(__assoc_sub_state* __state) : __state_(__state) { __state_->__attach_future();… in future() function in future
129 future<void>::~future() { in ~future()
134 void future<void>::get() { in get()
153 future<void> promise<void>::get_future() { in get_future()
156 return future<void>(__state_); in get_future()
/src/contrib/llvm-project/libcxx/modules/std/
H A Dfuture.inc33 // [futures.future.error], class future_error
43 // [futures.unique.future], class template future
44 using std::future;
46 // [futures.shared.future], class template shared_future
/src/crypto/openssl/test/radix/
H A DREADME.md14 - multi-process (in future)
15 - multi-node (in future)
19 other protocols in future if desired.
23 supported by the RADIX test framework in future include:
31 given to support of multi-process and multi-node testing in the future, though
47 to operations. Other kinds of object could be supported in future if needed.
77 - In the future, multi-process or multi-node testing will be supported.
86 used for testing other protocols in the future. There is a clean, layered
/src/crypto/openssl/doc/designs/quic-design/
H A Dcongestion-control.md5 use of pluggable QUIC congestion controllers in the future. The interface is
20 controller makes use of this facility, it can be used by future congestion
31 a clock. In the future it is likely that access at least to the statistics
40 per connection. This may change in future.
54 controllers via a provider-based interface in the future.
H A Dquic-requirements.md25 record layer interface will be internal only for MVP and be public in a future
87 existing (or future) security protocols and to select between them with minimal
101 to work in a QUIC environment while expanding our APIs to enable future
109 in a future OpenSSL release will be provided.
160 * QUIC performance should be comparable (in some future release - not MVP) with
165 support "single copy" APIs in the future:
/src/sys/contrib/openzfs/module/icp/asm-arm/sha2/
H A Dsha256-armv7.S135 ldr r2,[sp,#2*4] @ from future BODY_16_xx
137 ldr r1,[sp,#15*4] @ from future BODY_16_xx
193 ldr r2,[sp,#3*4] @ from future BODY_16_xx
195 ldr r1,[sp,#0*4] @ from future BODY_16_xx
251 ldr r2,[sp,#4*4] @ from future BODY_16_xx
253 ldr r1,[sp,#1*4] @ from future BODY_16_xx
309 ldr r2,[sp,#5*4] @ from future BODY_16_xx
311 ldr r1,[sp,#2*4] @ from future BODY_16_xx
367 ldr r2,[sp,#6*4] @ from future BODY_16_xx
369 ldr r1,[sp,#3*4] @ from future BODY_16_xx
[all …]
/src/sys/crypto/openssl/arm/
H A Dsha256-armv4.S179 ldr r2,[sp,#2*4] @ from future BODY_16_xx
181 ldr r1,[sp,#15*4] @ from future BODY_16_xx
237 ldr r2,[sp,#3*4] @ from future BODY_16_xx
239 ldr r1,[sp,#0*4] @ from future BODY_16_xx
295 ldr r2,[sp,#4*4] @ from future BODY_16_xx
297 ldr r1,[sp,#1*4] @ from future BODY_16_xx
353 ldr r2,[sp,#5*4] @ from future BODY_16_xx
355 ldr r1,[sp,#2*4] @ from future BODY_16_xx
411 ldr r2,[sp,#6*4] @ from future BODY_16_xx
413 ldr r1,[sp,#3*4] @ from future BODY_16_xx
[all …]
/src/contrib/llvm-project/clang/include/clang/CodeGen/
H A DConstantInitFuture.h95 static inline void *getAsVoidPointer(T future) {
96 return future.getOpaqueValue();
/src/contrib/ntp/adjtimed/
H A DREADME7 future HP-UX releases. Perhaps HP-UX will have a real adjtime(2)
8 system call in the future.
/src/crypto/openssl/doc/man3/
H A DEVP_set_default_properties.pod7 - manage default properties for future algorithm fetches
21 future EVP algorithm fetches, implicit as well as explicit. See
32 EVP_get1_default_properties() gets the default properties set for all future EVP
H A DCT_POLICY_EVAL_CTX_new.pod97 issued in the future. RFC6962 states that "TLS clients MUST reject SCTs whose
98 timestamp is in the future". By default, this will be set to 5 minutes in the
99 future (e.g. (time() + 300) * 1000), to allow for clock drift.
H A DBIO_f_prefix.pod30 BIO_set_prefix() sets the prefix to be used for future lines of
35 BIO_set_indent() sets the indentation to be used for future lines of
/src/contrib/tzdata/
H A DNEWS13 Changes to past and future timestamps
22 Europe/Athens for future timestamps.
240 Changes to future timestamps
267 Changes to future timestamps
408 with Asia/Tashkent for future timestamps, due to Kazakhstan's
466 Changes to future timestamps
535 Changes to future timestamps
547 Changes to past and future timestamps
632 Changes to past and future timestamps
640 Changes to future timestamps
[all …]
/src/contrib/tzcode/
H A DNEWS13 Changes to past and future timestamps
22 Europe/Athens for future timestamps.
240 Changes to future timestamps
267 Changes to future timestamps
408 with Asia/Tashkent for future timestamps, due to Kazakhstan's
466 Changes to future timestamps
535 Changes to future timestamps
547 Changes to past and future timestamps
632 Changes to past and future timestamps
640 Changes to future timestamps
[all …]
/src/crypto/openssl/doc/designs/
H A Dthread-api.md17 providing more flexible or advanced usage may be added in future releases.
74 * future.
96 future.
/src/tools/build/options/
H A DWITH_PROFILE3 This option is deprecated and may not be present in a future version of
H A DLIBC_MALLOC11 Other implementations are expected in the future in both
H A DWITH_UNIFIED_OBJDIR8 This option is transitional and will be removed in a future version of
/src/sbin/pfctl/tests/files/
H A Dpf0052.in1 # test setting all optimizations to avoid future keyword clashes
/src/crypto/openssl/doc/designs/quic-design/server/
H A Dquic-server-api.md20 - Support connection migration and preferred addressing in the future.
35 cases in the future. For example, it could be used for TLS over TCP to make
42 support DTLS in the future in the same way as QUIC, etc.
105 * TCP and DTLS can be supported in the future; not supported for non-QUIC
153 /* Returns 1 for QLSOs (or future TLS/DTLS listeners) only. */
337 Thus, this API should be compatible with any future adaptation to also support
343 so this API should also be adaptable to support DTLS in the future, providing
358 theoretically possible in future and is discussed in the next section.
398 A domain could contain multiple QLSOs (i.e., multiple UDP sockets) in future.
453 intended to demonstrate potential future directions and the adaptability of the
[all …]
/src/share/doc/papers/jail/
H A DMakefile4 EXTRA= implementation.ms mgt.ms future.ms jail01.eps
/src/sys/contrib/openzfs/module/zstd/
H A DREADME.md17 future. Thus we keep them private to Zstd.
55 to add future compatibility checks and/or fixes. However, currently it is
/src/contrib/ntp/
H A Dreadme.y2kfixes38 upgrades, and tests within legal future distributions as long as
62 including publishing in future Y2K related release notes,
64 persons... appropriate credit will be given in any future
/src/crypto/openssl/doc/internal/man7/
H A Ddeprecation.pod53 future, but needs to remain available until that time.
69 In the future, when the deprecated declaration is to actually be removed
94 For a deprecated function that we plan to remove in the future, for example

12345678910>>...17