Lines Matching full:can

12 that can be intercepted by the framework for debugging or tracing purposes,
23 single stream of text that can be gigantic and requires tedious crawling through
25 and analyzing it can be very time consuming and often not very practical beyond
49 There are no constraints on the granularity of an “action”, it can be as simple
54 /// A custom Action can be defined minimally by deriving from
63   /// This tag should uniquely identify this action, it can be matched for filtering
71 Any transformation can then be dispatched with this `Action` through the
84 An action can also carry arbitrary payload, for example we can extend the
88 /// A custom Action can be defined minimally by deriving from
89 /// `tracing::ActionImpl`. It can have any members!
95   /// Other constructor arguments can also be required here.
98   /// This tag should uniquely identify this action, it can be matched for filtering
103   /// Extra members can be carried by the Action
125 When a transformation is executed through an `Action`, it can be directly
126 intercepted via a handler that can be set on the `MLIRContext`:
129   /// Signatures for the action handler that can be registered with the context.
134   /// context. A nullptr handler can be set to disable a previously set handler.
140 handler has full control of the execution, as such it can also decide to return
164 With a bit of tooling, the values to use for the counter can be automatically
202 For example, using the options above we can see how many times an action is
225 - Multiple `Observers` can be registered with the `ExecutionContext`. When an
228 - Multiple `BreakpointManager` can be registered with the `ExecutionContext`.
235   `using CallbackTy = function_ref<Control(const ActionActiveStack *)>;` can be
254   Since the callback actually controls the execution, there can be only one
261 execution. It can be setup with
264 function that can be called from a debugger to:
272 The implementation of this runtime can serve as an example for other
278 stream. It can be exercised with `mlir-opt` using `--log-actions-to=<filename>`,