[PM] Fix a silly bug in my recent update to the CG update logic.

I used the wrong variable to update. This was even covered by a unittest
I wrote, and the comments for the unittest were correct (if confusing)
but the test itself just matched the buggy behavior. =[

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@307764 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Chandler Carruth
2017-07-12 09:08:11 +00:00
parent 8577619105
commit 3870ce243f
2 changed files with 7 additions and 7 deletions
+1 -1
View File
@@ -373,7 +373,7 @@ incorporateNewSCCRange(const SCCRangeT &NewSCCRange, LazyCallGraph &G,
// Ensure new SCCs' function analyses are updated.
if (NeedFAMProxy)
updateNewSCCFunctionAnalyses(*C, G, AM);
updateNewSCCFunctionAnalyses(NewC, G, AM);
// Also propagate a normal invalidation to the new SCC as only the current
// will get one from the pass manager infrastructure.