David Majnemer 00428878bb InstSimplify: Fix a bug when INT_MIN is in a sdiv ...

When INT_MIN is the numerator in a sdiv, we would not properly handle
overflow when calculating the bounds of possible values; abs(INT_MIN) is
not a meaningful number.

Instead, check and handle INT_MIN by reasoning that the largest value is
INT_MIN/-2 and the smallest value is INT_MIN.

This fixes PR20199.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@212307 91177308-0d34-0410-b5e6-96231b3b80d8

2014-07-04 00:23:39 +00:00

..

2010-12-20-Boolean.ll

…

2011-01-14-Thread.ll

…

2011-02-01-Vector.ll

…

2011-09-05-InsertExtractValue.ll

…

2011-10-27-BinOpCrash.ll

…

2011-11-23-MaskedBitsCrash.ll

…

2013-04-19-ConstantFoldingCrash.ll

…

AndOrXor.ll

…

apint-or.ll

Move optimization of some cases of (A & C1)|(B & C2) from instcombine to instsimplify. Patch by Rahul Jain, plus some last minute changes by me -- you can blame me for any bugs.

2014-06-19 03:51:46 +00:00

call-callconv.ll

…

call.ll

…

compare.ll

InstSimplify: Fix a bug when INT_MIN is in a sdiv

2014-07-04 00:23:39 +00:00

dead-code-removal.ll

…

exact-nsw-nuw.ll

…

fast-math.ll

…

fdiv.ll

…

floating-point-arithmetic.ll

…

maxmin.ll

…

past-the-end.ll

…

phi.ll

…

ptr_diff.ll

…

reassociate.ll

…

rem.ll

…

undef.ll

…

vector_gep.ll

…