Lines Matching defs:Ir
114 CLG_DEBUG(6, "log_global_event: Ir %#lx/%u\n",
143 CLG_DEBUG(6, "log_cond_branch: Ir %#lx, taken %ld\n",
173 CLG_DEBUG(6, "log_ind_branch: Ir %#lx, dst %#lx\n",
201 the sense that no IR has yet been generated to do the relevant
212 At various points the list will need to be flushed, that is, IR
223 instrumentation IR for each event, in the order in which they
226 For example, it could well be profitable to handle two adjacent Ir
251 } Ir;
334 VG_(printf)("Ir (InstrInfo %p) at +%u\n",
397 // Ir event always is first for a guest instruction
440 /* generate IR to notify event i and possibly the ones
460 /* Merge an Ir with a following Dr. */
462 /* Why is this true? It's because we're merging an Ir
463 with a following Dr. The Ir derives from the
468 immediately preceding Ir. Same applies to analogous
479 /* Merge an Ir with a following Dw/Dm. */
491 /* Merge an Ir with two following Irs. */
502 /* Merge an Ir with one following Ir. */
774 resulting cost offset depend on events (Ir/Dr/Dw/Dm) in guest
982 /* Set up SB for instrumented IR */
985 // Copy verbatim any IR preamble preceding the first IMark
1284 /* shouldn't happen - if the incoming IR is properly
