Lines Matching full:increment
20 // Terminology note: this code has a lot of handling for "post-increment" or
21 // "post-inc" users. This is not talking about post-increment addressing modes;
32 // example, the icmp is a post-increment user, since it uses %i.next, which is
33 // the value of the induction variable after the increment. The other common
34 // case of post-increment users is users outside the loop.
47 // multiple base registers, or as the increment expression in an addrec),
668 /// TODO: Allow UDivExpr if we can find an existing IV increment that is an
1422 /// IVInc - An individual increment in a Chain of IV increments.
1444 /// ChainUsers - Helper for CollectChains to track multiple IV increment uses.
1464 /// induction variable increment should be placed. In simple loops, this is
1466 /// position which will dominate all the in-loop post-increment users.
1485 // have more than a few IV increment chains in a loop. Missing a Chain falls
1702 /* create new increment. '++d' in above example. */
2020 // Determine an insertion point for the loop induction variable increment. It
2317 /// Return true if the chain increment is profitable to expand into a loop
2319 /// increment will be an offset relative to the same base. We allow such offsets
2320 /// to potentially be used as chain increment as long as it's not obviously
2339 // We are not able to expand an increment unless it is loop invariant,
2345 // increment.
2422 // An IV chain with a single increment is handled by LSR's postinc
2428 // Materializing increment expressions in the preheader that didn't exist in
2452 // profitable loop invariant increment from the last link in the Chain.
2712 // Expand the IV increment.
2719 // If an IV increment can't be folded, use it as the next IV value.
2722 assert(IVTy == IVOper->getType() && "inconsistent IV increment type");
4148 // The expansion must also be dominated by the increment positions of any
4204 // Inform the Rewriter if we have a post-increment use, so that it can
