Home | History | Annotate | Download | only in jit

Lines Matching defs:recording

45    C API is implemented in terms of a gcc::jit::recording::context,
48    When a gcc_jit_context is compiled, the recording context creates a
54    recording, and those relating to playback:
56    * Visibility: recording objects are exposed back to client code,
59    * Lifetime: recording objects have a lifetime equal to that of the
60      recording context that created them, whereas playback objects only
63    * Memory allocation: recording objects are allocated by the recording
68    * Integration with rest of GCC: recording objects are unrelated to the
70      instances.  Hence you can't ask a recording rvalue or lvalue what its
74    * Instancing: There can be multiple recording contexts "alive" at once
79    finer-grained initialization, then this recording vs playback
82    During a playback, we associate objects from the recording with
84    within the recording objects, as ``void *m_playback_obj``, casting it to
89    GC-allocated, but the recording objects don't own references:
106 namespace recording {
108   /* Recording types.  */
138   /* End of recording types. */
168   dump (recording::context &ctxt,
173   recording::context &get_context () { return m_ctxt; }
180   recording::location *
186   recording::context &m_ctxt;