/external/webrtc/test/peer_scenario/tests/ |
D | remote_estimate_test.cc | 55 auto signaling = s.ConnectSignaling(caller, callee, send_link, ret_link); in TEST() local 58 signaling.NegotiateSdp( in TEST() 87 auto signaling = s.ConnectSignaling(caller, callee, {send_node}, {ret_node}); in TEST() local 89 signaling.StartIceSignaling(); in TEST() 92 signaling.NegotiateSdp( in TEST()
|
/external/perfetto/docs/design-docs/ |
D | heapprofd-wire-protocol.md | 13 …stacks and frees to heapprofd, we use a single shared memory buffer and signaling socket. The clie… 22 …ack objects and the shared memory buffer). When data is received on the signaling socket, the _Unw… 50 …signaling socket. The client uses those to finish initializing its internal state. The _Main Threa… 56 …raw stack onto the shared memory buffer, and then sends a byte over the signaling socket to wake u… 71 …om the client. It unmaps the shared memory, closes the memfd, and then closes the signaling socket. 79 …and the single signaling socket. Instead, the data is written to the shared memory buffer, and the…
|
/external/webrtc/test/peer_scenario/ |
D | peer_scenario.cc | 91 auto signaling = ConnectSignaling(caller, callee, send_link, ret_link); in SimpleConnection() local 92 signaling.StartIceSignaling(); in SimpleConnection() 94 signaling.NegotiateSdp( in SimpleConnection()
|
/external/mesa3d/docs/_extra/specs/ |
D | INTEL_shader_atomic_float_minmax.txt | 81 the contents of mem. If one of these is an IEEE signaling NaN (i.e., 86 IEEE signaling NaNs, the result of the comparison is undefined. 93 the contents of mem. If one of these is an IEEE signaling NaN (i.e., 98 signaling NaNs, the result of the comparison is undefined. 160 NaN. IEEE considers two different kinds of NaN: signaling NaN and quiet 162 a signaling NaN does not. This concept does not exist in SPIR-V, 164 signaling NaN. atomicMin and atomicMax specifically implement
|
/external/webrtc/docs/native-code/rtp-hdrext/video-content-type/ |
D | README.md | 11 SDP "a= name": "video-content-type" ; this is also used in client/cloud signaling.
|
/external/llvm-project/llvm/docs/GlobalISel/ |
D | GenericOpcode.rst | 425 In the case where a single input is a NaN (either signaling or quiet), 435 In the case where a single input is a NaN (either signaling or quiet), 444 definition. This differs from FMINNUM in the handling of signaling NaNs. If one 445 input is a signaling NaN, returns a quiet NaN. 451 definition. This differs from FMAXNUM in the handling of signaling NaNs. If one 452 input is a signaling NaN, returns a quiet NaN.
|
/external/webrtc/examples/objc/AppRTCMobile/ |
D | ARDAppClient.m | 152 // TODO(tkchin): Provide signaling channel factory interface so we can recreate 601 // signaling channel. The offer or answer message must be processed before other 602 // signaling messages, however they can arrive out of order. Hence, this method 615 // Processes the given signaling message based on its type. 655 // Sends a signaling message to the other client. The caller will send messages 657 // signaling channel.
|
D | ARDSignalingMessage.m | 41 RTCLogError(@"Error parsing signaling message JSON.");
|
/external/llvm-project/llvm/test/CodeGen/SystemZ/ |
D | fp-strict-cmps-06.ll | 1 ; Test f128 signaling comparisons on z14.
|
D | fp-strict-cmps-03.ll | 1 ; Test 128-bit floating-point signaling comparison. The tests assume a z10
|
D | vec-strict-cmps-03.ll | 1 ; Test signaling vector floating-point comparisons on z13.
|
D | fp-strict-cmps-05.ll | 2 ; eliminate *strict* signaling compares for load complement, load negative
|
D | fp-strict-cmps-04.ll | 1 ; Verify that floating-point strict signaling compares cannot be omitted
|
/external/webrtc/docs/native-code/rtp-hdrext/abs-send-time/ |
D | README.md | 12 SDP "a= name": "abs-send-time" ; this is also used in client/cloud signaling.
|
/external/libchrome/mojo/public/cpp/system/ |
D | README.md | 178 Any C++ handle type's last known signaling state can be queried by calling the 213 to watch a handle for signaling state changes. A `SimpleWatcher` is bound to a 232 return the watched handle to an uninteresting signaling state (by *e.g.*, 278 waiting for one or more handles to change signaling state in an interesting way. 352 sequence until either one of the handles attains an interesting signaling state 391 // signaling races with timeout, both things might be true.
|
/external/libchrome/mojo/public/c/system/ |
D | README.md | 596 **signaling state** which may be queried at any time. For example: 626 handles start out with the same signaling state: 633 Writing a message to handle `b` will eventually alter the signaling state of `a` 635 then close `b`, the signaling state of `a` would look like: 646 Finally if we read the last message from `a` its signaling state becomes: 657 The ability to query a handle's signaling state can be useful, but it's not 659 with the ability to **trap** changes in a handle's signaling state and 719 of signaling conditions. A handle may be watched simultaneously by multiple 741 signaling state change on a watched handle, it must first be armed. A trap may 799 * `blocking_events[0].signals_state` is the last known signaling state of handle
|
/external/webrtc/docs/native-code/rtp-hdrext/video-timing/ |
D | README.md | 11 SDP "a= name": "video-timing" ; this is also used in client/cloud signaling.
|
/external/swiftshader/third_party/llvm-10.0/llvm/include/llvm/IR/ |
D | ConstrainedOps.def | 50 // These are definitions for compare instructions (signaling and quiet version).
|
/external/pigweed/pw_sync/ |
D | docs.rst | 7 and/or interrupts through signaling primitives and critical section lock 958 Native signaling primitives tend to vary more compared to critial section locks 959 across different platforms. For example, although common signaling primtives 963 build any signaling primitive based on other native signaling primitives, this 966 For this reason, Pigweed intends to provide some "simpler" signaling primitives 970 This simpler but highly portable class of signaling primitives is intended to
|
/external/python/cpython2/Doc/library/ |
D | math.rst | 381 (where C99 Annex F recommends signaling invalid operation or divide-by-zero), 389 Note that Python makes no effort to distinguish signaling NaNs from 390 quiet NaNs, and behavior for signaling NaNs remains unspecified.
|
D | decimal.rst | 460 NaNs signal. That is, if neither operand is a signaling NaN then any 461 quiet NaN operand is treated as though it were a signaling NaN. 476 Quiet and signaling NaNs are also included in the total ordering. The 602 Return :const:`True` if the argument is a (quiet or signaling) NaN and 633 Return :const:`True` if the argument is a signaling NaN and :const:`False` 712 ignored (depending on the context and whether they are signaling or 726 ignored (depending on the context and whether they are signaling or 784 * ``"sNaN"``, indicating that the operand is a signaling NaN. 901 Round to the nearest integer, signaling :const:`Inexact` or 911 Round to the nearest integer without signaling :const:`Inexact` or [all …]
|
/external/llvm-project/llvm/include/llvm/IR/ |
D | ConstrainedOps.def | 64 // These are definitions for compare instructions (signaling and quiet version).
|
/external/python/cpython3/Doc/library/ |
D | decimal.rst | 499 NaNs signal. That is, if neither operand is a signaling NaN then any 500 quiet NaN operand is treated as though it were a signaling NaN. 513 Quiet and signaling NaNs are also included in the total ordering. The 626 Return :const:`True` if the argument is a (quiet or signaling) NaN and 646 Return :const:`True` if the argument is a signaling NaN and :const:`False` 704 ignored (depending on the context and whether they are signaling or 716 ignored (depending on the context and whether they are signaling or 766 * ``"sNaN"``, indicating that the operand is a signaling NaN. 876 Round to the nearest integer, signaling :const:`Inexact` or 884 Round to the nearest integer without signaling :const:`Inexact` or [all …]
|
/external/rust/crates/byteorder/ |
D | CHANGELOG.md | 93 unnecessary signaling NaN masking, and in turn, the `unsafe` annotations
|
/external/webrtc/docs/ |
D | faq.md | 34 * Builds on the strength of the web browser: WebRTC abstracts signaling by 35 offering a signaling state machine that maps directly to `PeerConnection`.
|