From fbcb3f11fc90e9f00e6074e9b118b8dc11ca604c Mon Sep 17 00:00:00 2001 From: Anna Zaks Date: Thu, 30 Aug 2012 23:42:02 +0000 Subject: [analyzer] Refactor the logic that determines if a functions should be reanalyzed. The policy on what to reanalyze should be in AnalysisConsumer with the rest of visitation order logic. There is no reason why ExprEngine needs to pass the Visited set to CoreEngine, it can populate it itself. git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@162957 91177308-0d34-0410-b5e6-96231b3b80d8 --- lib/StaticAnalyzer/Core/CoreEngine.cpp | 5 ----- 1 file changed, 5 deletions(-) (limited to 'lib/StaticAnalyzer/Core/CoreEngine.cpp') diff --git a/lib/StaticAnalyzer/Core/CoreEngine.cpp b/lib/StaticAnalyzer/Core/CoreEngine.cpp index 1f137424d4..8b7eeef470 100644 --- a/lib/StaticAnalyzer/Core/CoreEngine.cpp +++ b/lib/StaticAnalyzer/Core/CoreEngine.cpp @@ -243,11 +243,6 @@ void CoreEngine::dispatchWorkItem(ExplodedNode* Pred, ProgramPoint Loc, case ProgramPoint::CallEnterKind: { CallEnter CEnter = cast(Loc); - if (AnalyzedCallees) - if (const CallExpr* CE = - dyn_cast_or_null(CEnter.getCallExpr())) - if (const Decl *CD = CE->getCalleeDecl()) - AnalyzedCallees->insert(CD); SubEng.processCallEnter(CEnter, Pred); break; } -- cgit v1.2.3-18-g5258