From: Craig Topper <craig.topper@gmail.com>
Date: Sat, 3 Jun 2017 07:47:14 +0000 (+0000)
Subject: [LazyValueInfo] Use Type::getIntegerBitWidth instead of casting to IntegerType to... 
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=079f840dc0f55e2fadaf59e84897378b849ce1f5;p=llvm

[LazyValueInfo] Use Type::getIntegerBitWidth instead of casting to IntegerType to call getBitWidth. NFC

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

diff --git a/lib/Analysis/LazyValueInfo.cpp b/lib/Analysis/LazyValueInfo.cpp
index 5180f07eaa2..6a9ae6440ac 100644
--- a/lib/Analysis/LazyValueInfo.cpp
+++ b/lib/Analysis/LazyValueInfo.cpp
@@ -1213,8 +1213,7 @@ bool LazyValueInfoImpl::solveBlockValueCast(LVILatticeVal &BBLV,
       LHSRange = LHSVal.getConstantRange();
   }
 
-  const unsigned ResultBitWidth =
-    cast<IntegerType>(CI->getType())->getBitWidth();
+  const unsigned ResultBitWidth = CI->getType()->getIntegerBitWidth();
 
   // NOTE: We're currently limited by the set of operations that ConstantRange
   // can evaluate symbolically.  Enhancing that set will allows us to analyze