Sanjoy Das 4e31476ab1 [SCEV] Clarify behavior around max backedge taken count ... This change makes the split between the "exact" backedge taken count and the "maximum" backedge taken count a bit more obvious. Both of these are upper bounds on the number of times the loop header executes (since SCEV does not account for most kinds of abnormal control flow), but the latter is guaranteed to be a constant. There were a few places where the max backedge taken count *was* a non-constant; I've changed those to compute constants instead. At this point, I'm not sure if the constant max backedge count can be computed by calling `getUnsignedRange(Exact).getUnsignedMax()` without losing precision. If it can, we can simplify even further by making `getMaxBackedgeTakenCount` a thin wrapper around `getBackedgeTakenCount` and `getUnsignedRange`. llvm-svn: 303497		2017-05-21 01:47:50 +00:00
..
llvm	[SCEV] Clarify behavior around max backedge taken count	2017-05-21 01:47:50 +00:00
llvm-c	Introduce LLVMDIBuilderRef	2017-04-20 14:22:47 +00:00