baloghadamsoftware added inline comments.
================
Comment at: lib/StaticAnalyzer/Frontend/AnalysisConsumer.cpp:452
@@ -444,5 +451,3 @@
// inlining when reanalyzing an already inlined function.
- if (Visited.count(D)) {
- assert(isa<ObjCMethodDecl>(D) &&
- "We are only reanalyzing ObjCMethods.");
+ if (Visited.count(D) && isa<ObjCMethodDecl>(D)) {
const ObjCMethodDecl *ObjCM = cast<ObjCMethodDecl>(D);
----------------
I made a quick measurement on our build server using clang as target code.
Real/user/system times were 75/575/18 for minimal and 76/587/18 for regular.
This does not seem too much. However, since the semantics of a copy assignment
operator is often composed of the semantics of a destructor and the semantics
of a copy constructor implementations often put these two functionalities into
separate functions and call them from the destructor, copy constructor and copy
assignment operator. Such implementations requires regular inlining to be
checked.
http://reviews.llvm.org/D19311
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
