From: Craig Topper <craig.topper@intel.com>
Date: Fri, 9 Jun 2017 21:21:17 +0000 (+0000)
Subject: [LVI] Fix spelling error in comment. NFC
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=24ed17e2405e7f2d8640b814cc9e1388000b22d1;p=llvm

[LVI] Fix spelling error in comment. NFC

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

diff --git a/lib/Analysis/LazyValueInfo.cpp b/lib/Analysis/LazyValueInfo.cpp
index 9fd196e4156..3ed61a79478 100644
--- a/lib/Analysis/LazyValueInfo.cpp
+++ b/lib/Analysis/LazyValueInfo.cpp
@@ -806,7 +806,7 @@ bool LazyValueInfoImpl::solveBlockValueImpl(LVILatticeVal &Res,
   // that for all other pointer typed values, we terminate the search at the
   // definition.  We could easily extend this to look through geps, bitcasts,
   // and the like to prove non-nullness, but it's not clear that's worth it
-  // compile time wise.  The context-insensative value walk done inside
+  // compile time wise.  The context-insensitive value walk done inside
   // isKnownNonNull gets most of the profitable cases at much less expense.
   // This does mean that we have a sensativity to where the defining
   // instruction is placed, even if it could legally be hoisted much higher.