forked from OSchip/llvm-project
cf10ea8cb2
Previously our edges were completely broken here; now, the final result is a very simple set of edges in most cases: one up to the "for" keyword for context, and one into the body of the loop. This matches the behavior for ObjC for-in loops. In the AST, however, CXXForRangeStmts are handled very differently from ObjCForCollectionStmts. Since they are specified in terms of equivalent statements in the C++ standard, we actually have implicit AST nodes for all of the semantic statements. This makes evaluation very easy, but diagnostic locations a bit trickier. Fortunately, the problem can be generally defined away by marking all of the implicit statements as part of the top-level for-range statement. One of the implicit statements in a for-range statement is the declaration of implicit iterators __begin and __end. The CFG synthesizes two separate DeclStmts to match each of these decls, but until now these synthetic DeclStmts weren't in the function's ParentMap. Now, the CFG keeps track of its synthetic statements, and the AnalysisDeclContext will make sure to add them to the ParentMap. <rdar://problem/14038483> llvm-svn: 183449 |
||
|---|---|---|
| .. | ||
| AnalysisDeclContext.cpp | ||
| BodyFarm.cpp | ||
| BodyFarm.h | ||
| CFG.cpp | ||
| CFGReachabilityAnalysis.cpp | ||
| CFGStmtMap.cpp | ||
| CMakeLists.txt | ||
| CallGraph.cpp | ||
| CocoaConventions.cpp | ||
| Dominators.cpp | ||
| FormatString.cpp | ||
| FormatStringParsing.h | ||
| LiveVariables.cpp | ||
| Makefile | ||
| ObjCNoReturn.cpp | ||
| PostOrderCFGView.cpp | ||
| PrintfFormatString.cpp | ||
| ProgramPoint.cpp | ||
| PseudoConstantAnalysis.cpp | ||
| ReachableCode.cpp | ||
| ScanfFormatString.cpp | ||
| ThreadSafety.cpp | ||
| UninitializedValues.cpp | ||