]> granicus.if.org Git - llvm/commit
[LazyValueInfo] Don't run the more complex predicate handling code for EQ and NE...
authorCraig Topper <craig.topper@intel.com>
Fri, 9 Jun 2017 16:16:20 +0000 (16:16 +0000)
committerCraig Topper <craig.topper@intel.com>
Fri, 9 Jun 2017 16:16:20 +0000 (16:16 +0000)
commitc65472c75feef22ce3c716aa14e24c5d3f2b3d51
tree940a3adc4f47d716bb750e1ab030caf47de86f4d
parent7ed47635a1f14e06c17fa251a046cbec7cd919cb
[LazyValueInfo] Don't run the more complex predicate handling code for EQ and NE in getPredicateResult

Summary:
Unless I'm mistaken, the special handling for EQ/NE should cover everything and there is no reason to fallthrough to the more complex code. For that matter I'm not sure there's any reason to special case EQ/NE other than avoiding creating temporary ConstantRanges.

This patch moves the complex code into an else so we only do it when we are handling a predicate other than EQ/NE.

Reviewers: anna, reames, resistor, Farhana

Reviewed By: anna

Subscribers: llvm-commits

Differential Revision: https://reviews.llvm.org/D34000

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@305086 91177308-0d34-0410-b5e6-96231b3b80d8
lib/Analysis/LazyValueInfo.cpp