| /freebsd/contrib/llvm-project/llvm/lib/Support/ |
| H A D | APFloat.cpp | 37 llvm_unreachable("Unexpected semantics"); \
102 /* Represents floating point arithmetic semantics. */
116 /* Number of bits actually used in the semantics. */
122 // Returns true if any number described by this semantics can be precisely
123 // represented by the specified semantics. Does not take into account
156 /* The IBM double-double semantics. Such a number consists of a pair of IEEE
167 /* These are legacy semantics for the fallback, inaccrurate implementation of
179 Currently, these semantics are used in the following way:
190 semantics. */
194 const llvm::fltSemantics &APFloatBase::EnumToSemantics(Semantics S) { in EnumToSemantics()
[all …]
|
| /freebsd/contrib/llvm-project/llvm/include/llvm/ADT/ |
| H A D | APFloat.h | 31 llvm_unreachable("Unexpected semantics"); \
78 /// full extended precision). Adding a new format that obeys IEEE semantics
150 /// \name Floating Point Semantics.
152 enum Semantics { enum
212 static const llvm::fltSemantics &EnumToSemantics(Semantics S);
213 static Semantics SemanticsToEnum(const llvm::fltSemantics &Sem);
307 /// semantics.
445 const fltSemantics &getSemantics() const { return *semantics; } in getSemantics()
452 /// magnitude in the current semantics.
456 /// number in the given semantics.
[all …]
|
| H A D | APFixedPoint.h | 30 /// The fixed point semantics work similarly to fltSemantics. The width
77 /// Return the number of integral bits represented by these semantics. These
86 /// of both input values. This does not compute the resulting semantics for a
91 /// Print semantics for debug purposes
150 /// semantics including the one used by fixed point types proposed in ISO/IEC
151 /// JTC1 SC22 WG14 N1169. The class carries the value and semantics of
180 // Convert this number to match the semantics provided. If the overflow
187 // value will be in the common, full precision semantics that can represent
231 /// provided semantics.
270 /// and in the same semantics as the provided target semantics. If the value
[all …]
|
| /freebsd/share/man/man9/ |
| H A D | atomic.9 | 110 Except as noted below, the semantics of these operations are almost
111 identical to the semantics of similarly named C11 atomic operations.
174 semantics.
182 The second variant has acquire semantics, and the third variant has release
183 semantics.
185 When an atomic operation has acquire semantics, the operation must have
188 Conversely, acquire semantics do not require that prior loads or stores have
190 An atomic operation can only have acquire semantics if it performs a load
192 To denote acquire semantics, the suffix
201 When an atomic operation has release semantics, all prior loads or stores
[all …]
|
| H A D | extattr.9 | 39 The semantics of this additional data is that of a "name=value" pair, where
52 The semantics of these attributes are intended to be as follows: user
70 should be used with awareness of the underlying semantics of the supporting
77 Depending on underlying file system semantics, this name may or may not be
|
| H A D | mac.9 | 61 must be aware of the semantics of the API calls, particularly with respect
87 Similarly, the caller must be aware of the reference counting semantics
104 Module writers must be aware of the locking semantics of entry points
106 or reference counting semantics for each argument, and modules must follow
135 confusion regarding lock orders and semantics.
|
| /freebsd/crypto/openssl/doc/designs/quic-design/ |
| H A D | quic-api.md | 90 | Semantics | API | Status |
131 - **Semantics**: This can be one of:
133 - **Unchanged**: The semantics of this existing libssl API call are
135 - **Changed**: The semantics are changed for QUIC.
171 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
177 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
182 we do not implement server support at this time. However, the semantics of this
187 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
193 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
201 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
[all …]
|
| H A D | quic-io-arch.md | 30 - 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 …]
|
| /freebsd/lib/libc/rpc/ |
| H A D | netconfig.5 | 16 describing their semantics and protocol.
23 .Ar network_id semantics flags family protoname device libraries
29 .It Ar semantics
30 Describes the semantics of the transport.
115 unsigned long nc_semantics; /* Semantics */
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | openssl-quic.7 | 167 for TLS connections and do not have changed semantics, with some exceptions. The
168 changes to the semantics of existing APIs are as follows:
172 semantics. There are broadly four options for applications to use as a network
180 semantics, and is recommended for existing applications which use a BIO pair or
184 datagram semantics. Unlike \fBBIO_s_dgram_pair\fR\|(3), it is unidirectional.
205 application can still enjoy blocking semantics for calls to application-level
332 of such a buffer is incompatible with QUIC as QUIC requires datagram semantics
340 \&\fBBIO_s_dgram_pair\fR\|(3) instead, which has the necessary datagram semantics. You
342 and to use datagram semantics when interacting with the \fBBIO_s_dgram_pair\fR\|(3)
349 semantics. \fBBIO_sendmmsg\fR\|(3) and \fBBIO_recvmmsg\fR\|(3) must be implemented. These
[all …]
|
| /freebsd/lib/libc/posix1e/ |
| H A D | acl.3 | 50 extensions defined that allow for ACL semantics alternative to
133 the ACL has POSIX.1e or NFSv4 semantics.
137 and may be used to determine whether the ACL has POSIX.1e or NFSv4 semantics.
222 and may be used to generate a text-form of a POSIX.1e or NFSv4 semantics ACL.
231 and may be used to validate an ACL as correct POSIX.1e-semantics, or
232 as appropriate for a particular file system object regardless of semantics.
|
| H A D | acl_valid.3 | 56 checks this validity only with POSIX.1e ACL semantics, and irrespective
74 For POSIX.1e semantics, the checks include:
135 The file system rejects the ACL based on fs-specific semantics issues.
|
| /freebsd/sys/contrib/device-tree/Bindings/mips/cavium/ |
| H A D | ciu3.txt | 13 The second cell indicates the triggering semantics, and may have a
14 value of either 4 for level semantics, or 1 for edge semantics.
|
| /freebsd/contrib/llvm-project/llvm/lib/Target/RISCV/ |
| H A D | RISCVISelLowering.h | 68 // RV64I shifts, directly matching the semantics of the named RISC-V
79 // RV64IB rotates, directly matching the semantics of the named RISC-V
83 // RV64IZbb bit counting instructions directly matching the semantics of the
94 // FMV_H_X matches the semantics of the FMV.H.X.
97 // FMV_W_X_RV64 matches the semantics of the FMV.W.X.
132 // Floating point fmax and fmin matching the RISC-V instruction semantics.
158 // VMV_V_V_VL matches the semantics of vmv.v.v but includes an extra operand
162 // VMV_V_X_VL matches the semantics of vmv.v.x but includes an extra operand
166 // VFMV_V_F_VL matches the semantics of vfmv.v.f but includes an extra operand
170 // VMV_X_S matches the semantics of vmv.x.s. The result is always XLenVT sign
[all …]
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | openssl-quic.pod | 127 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. L<BIO_sendmmsg(3)> and L<BIO_recvmmsg(3)> must be implemented. These
[all …]
|
| /freebsd/lib/libsys/ |
| H A D | eventfd.2 | 44 creates a special file descriptor with event counter or semaphore semantics,
63 use semaphore semantics
66 File operations have the following semantics:
122 the following semantics apply:
|
| /freebsd/share/man/man5/ |
| H A D | elf.5 | 502 This segment type is reserved but has unspecified semantics.
516 are reserved for processor-specific semantics.
520 are reserved for processor-specific semantics.
615 are reserved for processor-specific semantics.
619 are reserved for processor-specific semantics.
678 This member categorizes the section's contents and semantics.
740 This section is reserved but has unspecified semantics.
750 are reserved for processor-specific semantics.
754 are reserved for processor-specific semantics.
795 semantics.
[all …]
|
| /freebsd/contrib/llvm-project/clang/lib/StaticAnalyzer/Checkers/ |
| H A D | PthreadLockChecker.cpp | 14 // * C11LockChecker which also closely follows Pthread semantics.
230 LockingSemantics Semantics, CheckerKind CheckKind) const;
246 LockingSemantics Semantics, CheckerKind CheckKind) const;
307 // When a lock is destroyed, in some semantics(like PthreadSemantics) we are not
428 enum LockingSemantics Semantics, in AcquireLockAux() argument
460 switch (Semantics) { in AcquireLockAux()
468 llvm_unreachable("Unknown tryLock locking semantics"); in AcquireLockAux()
475 } else if (Semantics == PthreadSemantics) { in AcquireLockAux()
487 // XNU locking semantics return void on non-try locks in AcquireLockAux()
488 assert((Semantics == XNUSemantics) && "Unknown locking semantics"); in AcquireLockAux()
[all …]
|
| /freebsd/cddl/contrib/opensolaris/cmd/dtrace/test/tst/common/translators/ |
| H A D | tst.TestTransStability1.ksh.out | 6 Data Semantics: Unstable
11 Data Semantics: Stable
|
| H A D | tst.TestTransStability2.ksh.out | 6 Data Semantics: Unstable
11 Data Semantics: Private
|
| /freebsd/contrib/kyua/utils/ |
| H A D | auto_array.hpp | 48 /// Wrapper class to provide reference semantics for utils::auto_array.
67 /// A simple smart pointer for arrays providing strict ownership semantics.
69 /// This class is the counterpart of std::unique_ptr for arrays. The semantics of
|
| /freebsd/contrib/llvm-project/lld/ELF/ |
| H A D | Relocations.h | 84 // of a relocation type, there are some relocations whose semantics are
111 // Same as R_PC but with page-aligned semantics.
113 // Same as R_PLT_PC but with page-aligned semantics.
115 // In addition to having page-aligned semantics, LoongArch GOT relocs are
116 // also reused for TLS, making the semantics differ from other architectures.
|
| /freebsd/share/doc/psd/05.sysman/ |
| H A D | 2.3.t | 52 abstract type, which describes the semantics of communication using that
65 The SOCK_DGRAM type models the semantics of datagrams in network communication:
69 The SOCK_RDM type models the semantics of reliable datagrams: messages
85 and interfaces; it has no specific semantics.
90 This protocol is used within the domain to provide the semantics
|
| /freebsd/share/man/man3/ |
| H A D | pthread_multi_np.3 | 45 The semantics of this function is similar to
51 The semantics of this function is similar to
|
| /freebsd/contrib/llvm-project/llvm/lib/Transforms/Instrumentation/ |
| H A D | PoisonChecking.cpp | 9 // Implements a transform pass which instruments IR such that poison semantics
11 // semantics for every instruction w.r.t. poison as specified in the LLVM
13 // is focused purely on the semantics of LLVM IR, not any particular source
17 // The rewritten semantics of each instruction will include the following
342 Instructions w/Unclear Semantics:
351 Cases of clear poison semantics not yet implemented:
|