Lines Matching full:when

42 ///   // When the log implementation has had the chance to initialize, we can
89 /// implementation first. Some implementations might stay in an "off" state when
114   /// When an implementation is done initializing, it MUST return
115   /// XRAY_LOG_INITIALIZED. When users call `__xray_patch()`, they are
127   /// When an implementation is done finalizing, it MUST return
143 /// This enum indicates the installation state of a logging implementation, when
154 /// pointers in XRayLogImpl when being installed through `__xray_set_log_impl`.
166   /// when called.
177   /// when called.
189   /// The log implementation provided routine for when __xray_log_flushLog() is
193   /// when called.
210 ///   - When the implementation is UNINITIALIZED.
211 ///   - When the implementation is FINALIZED.
212 ///   - When there is no current implementation installed.
214 /// It is logging implementation defined what happens when this function is
224 /// identifier used when retrieving the log impl.
228 ///   - XRAY_DUPLICATE_MODE when an implementation is already associated with
260 ///   - When the implementation is UNINITIALIZED.
261 ///   - When the implementation is FINALIZED.
262 ///   - When there is no current implementation installed.
264 /// It is logging implementation defined what happens when this function is
278 /// NOTE: When this API is used, we still invoke the installed initialization
288 /// FIXME: Updating the XRayLogImpl struct is an ABI breaking change. When we
316 /// returns another XRayBuffer function representing the next buffer. When the