HomeSort by relevance Sort by last modified time
    Searched refs:PutI (Results 1 - 9 of 9) sorted by null

  /external/valgrind/main/VEX/priv/
ir_opt.c 97 * Redundant-PutI removal
114 * If block contains GetI or PutI, Expensive transformations.
117 - Unrolled a loop, and block does not contain GetI or PutI:
120 - Unrolled a loop, and block contains GetI or PutI:
132 accessed using GetI/PutI, and there is no need so far for them to
396 e1 = flatten_Expr(bb, st->Ist.PutI.ix);
397 e2 = flatten_Expr(bb, st->Ist.PutI.data);
398 addStmtToIRSB(bb, IRStmt_PutI(st->Ist.PutI.descr,
400 st->Ist.PutI.bias,
625 key = mk_key_GetIPutI( st->Ist.PutI.descr )
    [all...]
ir_defs.c     [all...]
host_x86_isel.c     [all...]
host_amd64_isel.c     [all...]
host_ppc_isel.c     [all...]
  /external/valgrind/main/memcheck/
mc_translate.c 86 6. As the index in a GETI or PUTI operation. I'm not sure why... (njn).
    [all...]
  /external/valgrind/main/VEX/pub/
libvex_ir.h 95 the "GetI" and "PutI" primitives. This is necessary to describe
    [all...]
  /external/valgrind/main/coregrind/
m_translate.c 558 /* PutI or Dirty call which overlaps SP: complain. We can't
562 descr = st->Ist.PutI.descr;
591 VG_(core_panic)("vg_SP_update_pass: PutI or Dirty which overlaps SP");
    [all...]
  /external/valgrind/main/exp-ptrcheck/
h_main.c     [all...]

Completed in 152 milliseconds