Lines Matching defs:Ir
113 CLG_DEBUG(6, "log_global_event: Ir %#lx/%u\n",
142 CLG_DEBUG(6, "log_cond_branch: Ir %#lx, taken %lu\n",
172 CLG_DEBUG(6, "log_ind_branch: Ir %#lx, dst %#lx\n",
200 the sense that no IR has yet been generated to do the relevant
211 At various points the list will need to be flushed, that is, IR
222 instrumentation IR for each event, in the order in which they
225 For example, it could well be profitable to handle two adjacent Ir
250 } Ir;
333 VG_(printf)("Ir (InstrInfo %p) at +%d\n",
396 // Ir event always is first for a guest instruction
439 /* generate IR to notify event i and possibly the ones
459 /* Merge an Ir with a following Dr. */
461 /* Why is this true? It's because we're merging an Ir
462 with a following Dr. The Ir derives from the
467 immediately preceding Ir. Same applies to analogous
478 /* Merge an Ir with a following Dw/Dm. */
490 /* Merge an Ir with two following Irs. */
501 /* Merge an Ir with one following Ir. */
729 resulting cost offset depend on events (Ir/Dr/Dw/Dm) in guest
936 /* Set up SB for instrumented IR */
939 // Copy verbatim any IR preamble preceding the first IMark
1210 /* shouldn't happen - if the incoming IR is properly
