forked from OSchip/llvm-project
[ConstantRange] Fix the early out in ConstantRange::multiply for positive numbers to really do what the comment says
r271020 added an early out to skip the signed multiply portion of ConstantRange::multiply. The comment says we don't need to do signed multiply if the range is only positive numbers, but the implemented check only ensures that the start of the range is positive. It doesn't look at the end of the range. This patch checks the end of the range instead. Because Upper is one more than the end we have to see if its positive or if its one past the last positive number. llvm-svn: 302717
This commit is contained in:
parent
ef0114c4f0
commit
c51d05369a
|
@ -757,7 +757,8 @@ ConstantRange::multiply(const ConstantRange &Other) const {
|
|||
// from one positive number to another which is as good as we can generate.
|
||||
// In this case, skip the extra work of generating signed ranges which aren't
|
||||
// going to be better than this range.
|
||||
if (!UR.isWrappedSet() && UR.getLower().isNonNegative())
|
||||
if (!UR.isWrappedSet() &&
|
||||
(UR.getUpper().isNonNegative() || UR.getUpper().isMinSignedValue()))
|
||||
return UR;
|
||||
|
||||
// Now the signed range. Because we could be dealing with negative numbers
|
||||
|
|
|
@ -447,7 +447,7 @@ TEST_F(ConstantRangeTest, Multiply) {
|
|||
// TODO: This should be return [-2, 0]
|
||||
EXPECT_EQ(ConstantRange(APInt(8, -2)).multiply(
|
||||
ConstantRange(APInt(8, 0), APInt(8, 2))),
|
||||
ConstantRange(APInt(8, 0), APInt(8, 255)));
|
||||
ConstantRange(APInt(8, -2), APInt(8, 1)));
|
||||
}
|
||||
|
||||
TEST_F(ConstantRangeTest, UMax) {
|
||||
|
|
Loading…
Reference in New Issue