Home
last modified time | relevance | path

Searched refs:semantics (Results 1 – 25 of 170) sorted by relevance

1234567

/freebsd/contrib/llvm-project/llvm/lib/Support/
H A DAPFloat.cpp323 unsigned int APFloatBase::semanticsPrecision(const fltSemantics &semantics) { in semanticsPrecision() argument
324 return semantics.precision; in semanticsPrecision()
327 APFloatBase::semanticsMaxExponent(const fltSemantics &semantics) { in semanticsMaxExponent() argument
328 return semantics.maxExponent; in semanticsMaxExponent()
331 APFloatBase::semanticsMinExponent(const fltSemantics &semantics) { in semanticsMinExponent() argument
332 return semantics.minExponent; in semanticsMinExponent()
334 unsigned int APFloatBase::semanticsSizeInBits(const fltSemantics &semantics) { in semanticsSizeInBits() argument
335 return semantics.sizeInBits; in semanticsSizeInBits()
337 unsigned int APFloatBase::semanticsIntSizeInBits(const fltSemantics &semantics, in semanticsIntSizeInBits() argument
341 unsigned int MinBitWidth = semanticsMaxExponent(semantics) + 1; in semanticsIntSizeInBits()
[all …]
/freebsd/contrib/llvm-project/llvm/include/llvm/ADT/
H A DAPFloat.h445 const fltSemantics &getSemantics() const { return *semantics; } in getSemantics()
679 const fltSemantics *semantics; variable
818 const fltSemantics *semantics; member
842 if (usesLayout<IEEEFloat>(*semantics)) { in ~Storage()
846 if (usesLayout<DoubleAPFloat>(*semantics)) { in ~Storage()
854 if (usesLayout<IEEEFloat>(*RHS.semantics)) { in Storage()
858 if (usesLayout<DoubleAPFloat>(*RHS.semantics)) { in Storage()
866 if (usesLayout<IEEEFloat>(*RHS.semantics)) { in Storage()
870 if (usesLayout<DoubleAPFloat>(*RHS.semantics)) { in Storage()
878 if (usesLayout<IEEEFloat>(*semantics) &&
[all …]
/freebsd/sys/contrib/device-tree/Bindings/mips/cavium/
H A Dciu3.txt13 The second cell indicates the triggering semantics, and may have a
14 value of either 4 for level semantics, or 1 for edge semantics.
H A Dcib.txt19 CIB. The second cell specifies the triggering semantics of the
/freebsd/crypto/openssl/doc/designs/quic-design/
H A Dquic-io-arch.md30 - We want to support both blocking and non-blocking semantics
46 passed to the QUIC implementation be configured to support datagram semantics
47 instead of bytestream semantics as has been the case with traditional TLS
50 datagram semantics. These changes are not minor, but there is no way around this
73 To function correctly and provide blocking semantics at the application level,
115 can implement the required semantics above.
147 able to support blocking semantics at the application level. Applications
148 which require blocking semantics would only be able to function in thread
199 need to change to using network BIOs with datagram semantics. For applications
220 Note that this is orthogonal to whether we provide blocking I/O semantics to the
[all …]
H A Dquic-api.md133 - **Unchanged**: The semantics of this existing libssl API call are
135 - **Changed**: The semantics are changed for QUIC.
182 we do not implement server support at this time. However, the semantics of this
273 - Change semantics to only determine the return value based on if there is
305 - Preserve `SSL_clear` semantics at the handshake layer, reset all QUIC state
369 The changes to the semantics of these calls are as follows:
371 - The BIO MUST be a BIO with datagram semantics (this is a change relative to
469 is no longer viable, thus blocking semantics at the application level must be
622 state semantics if the application happens to call `SSL_handle_events`, until it
1196 with datagram semantics.
[all …]
/freebsd/crypto/openssl/doc/man7/
H A Dopenssl-quic.pod127 for TLS connections and do not have changed semantics, with some exceptions. The
128 changes to the semantics of existing APIs are as follows:
136 semantics. There are broadly four options for applications to use as a network
149 semantics, and is recommended for existing applications which use a BIO pair or
155 datagram semantics. Unlike L<BIO_s_dgram_pair(3)>, it is unidirectional.
183 application can still enjoy blocking semantics for calls to application-level
370 of such a buffer is incompatible with QUIC as QUIC requires datagram semantics
380 L<BIO_s_dgram_pair(3)> instead, which has the necessary datagram semantics. You
382 and to use datagram semantics when interacting with the L<BIO_s_dgram_pair(3)>
391 semantics
[all...]
H A Dossl-guide-quic-introduction.pod118 to QUIC at all, and others have altered semantics. You should refer to the
148 TLS assumes "stream" type semantics for its underlying transport layer protocol
149 (usually achieved by using TCP). However QUIC assumes "datagram" type semantics
H A Dossl_store.pod54 * OSSL_STORE_eof() simulates file semantics for any repository to signal
/freebsd/contrib/file/m4/
H A Dvisibility.m414 dnl semantics (see the 'vismain' test in glibc) and does not exist e.g. on
17 dnl dependent semantics.
/freebsd/lib/libc/rpc/
H A Dnetconfig8 # <network_id> <semantics> <flags> <protofamily> <protoname> \
H A Drpc_generic.c730 __rpc_seman2socktype(int semantics) in __rpc_seman2socktype() argument
732 switch (semantics) { in __rpc_seman2socktype()
/freebsd/contrib/llvm-project/clang/include/clang/Basic/
H A DOpenCLExtensions.def39 // * affects the OpenCL language semantics or its syntax,
45 // semantics in the language compared to the core standard. #pragma directive
/freebsd/contrib/googletest/googletest/include/gtest/internal/custom/
H A DREADME.md12 `testing::TempDir` for semantics and signature.
/freebsd/contrib/llvm-project/lldb/include/lldb/Utility/
H A DScalar.h113 bool FloatPromote(const llvm::fltSemantics &semantics);
210 static PromotionKey GetFloatPromoKey(const llvm::fltSemantics &semantics);
/freebsd/crypto/openssl/doc/man3/
H A DBIO_s_datagram.pod13 BIO_dgram_get_mtu_overhead - Network BIO with datagram semantics
34 which provide datagram semantics, such as UDP sockets. It is suitable for use
37 Because BIO_s_datagram() has datagram semantics, a single BIO_write() call sends
42 For a memory-based BIO which provides datagram semantics identical to those of
/freebsd/contrib/llvm-project/lldb/source/Utility/
H A DScalar.cpp194 bool Scalar::FloatPromote(const llvm::fltSemantics &semantics) { in FloatPromote() argument
200 m_float = llvm::APFloat(semantics); in FloatPromote()
206 if (GetFloatPromoKey(semantics) < GetFloatPromoKey(m_float.getSemantics())) in FloatPromote()
210 m_float.convert(semantics, llvm::APFloat::rmNearestTiesToEven, &ignore); in FloatPromote()
/freebsd/contrib/sendmail/test/
H A DREADME20 t_exclopen.c test for security-defeating semantics that an open with
/freebsd/contrib/llvm-project/clang/include/clang/AST/
H A DPropertiesBase.td273 def : Property<"semantics", UInt32> {
284 static_cast<llvm::APFloatBase::Semantics>(semantics));
289 def : Property<"semantics", FixedPointSemantics> {
296 return APValue(llvm::APFixedPoint(std::move(value), semantics));
315 def : Property<"semantics", UInt32> {
326 static_cast<llvm::APFloatBase::Semantics>(semantics));
/freebsd/contrib/llvm-project/clang/lib/StaticAnalyzer/Checkers/
H A DObjCUnusedIVarsChecker.cpp52 for (const Expr *sub : POE->semantics()) { in Scan()
/freebsd/contrib/libcbor/doc/source/
H A Dapi.rst13 The *libcbor* API closely follows the semantics outlined by `CBOR standard <https://tools.ietf.org/…
/freebsd/contrib/llvm-project/lld/docs/ELF/
H A Dwarn_backrefs.rst31 A consequence of the differing archive searching semantics is that the same
77 libraries like ``B``. Consider linking ``B`` with object semantics by
/freebsd/contrib/llvm-project/lldb/source/Core/
H A DDumpDataExtractor.cpp667 const llvm::fltSemantics &semantics = in DumpDataExtractor() local
674 (llvm::APFloat::getSizeInBits(semantics) + 7) / 8; in DumpDataExtractor()
678 llvm::APFloat apfloat(semantics, *apint); in DumpDataExtractor()
/freebsd/contrib/libcbor/doc/source/api/
H A Dtype_0_1.rst31 Due to their largely similar semantics, the following functions can be used for both Type 0 and Typ…
/freebsd/contrib/tcsh/config/
H A Dbsd4.434 * with the berkeley semantics, so we cannot use it there either.

1234567