Tim Northover 0f17fdc4c5 InstCombine: move hasOneUse check to the top of foldICmpAddConstant ... There were two combines not covered by the check before now, neither of which actually differed from normal in the benefit analysis. The most recent seems to be because it was just added at the top of the function (naturally). The older is from way back in 2008 (r46687) when we just didn't put those checks in so routinely, and has been diligently maintained since. llvm-svn: 341831		2018-09-10 14:26:44 +00:00
..
assume.ll
deref-bitcast-of-gep.ll
dereferenceable-and-aligned.ll
func-ptr-lsb.ll
get-pointer-base-with-const-off.ll
invariant.group.ll	Simplify recursive launder.invariant.group and strip	2018-07-12 23:55:20 +00:00
known-bits-from-range-md.ll
known-non-equal.ll
known-nonnull-at.ll	Fix aliasing of launder.invariant.group	2018-05-23 09:16:44 +00:00
known-power-of-two.ll
known-signbit-shift.ll
knownnonzero-shift.ll
knownzero-addrspacecast.ll
knownzero-shift.ll
memory-dereferenceable.ll
monotonic-phi.ll
non-negative-phi-bits.ll	InstCombine: move hasOneUse check to the top of foldICmpAddConstant	2018-09-10 14:26:44 +00:00
numsignbits-from-assume.ll	Fix llvm::ComputeNumSignBits with some operations and llvm.assume	2018-07-25 16:39:24 +00:00
pr23011.ll
select-pattern.ll
signbits-extract-elt.ll