From 2e4067226bd243e384e71ae45de1275969e7dfe2 Mon Sep 17 00:00:00 2001 From: Kristof Umann Date: Tue, 21 Aug 2018 10:47:19 +0000 Subject: [analyzer][UninitializedObjectChecker] Added documentation to the checker list Differential Revision: https://reviews.llvm.org/D50904 llvm-svn: 340266 --- .../UninitializedObject/UninitializedObjectChecker.cpp | 12 ------------ 1 file changed, 12 deletions(-) (limited to 'clang/lib') diff --git a/clang/lib/StaticAnalyzer/Checkers/UninitializedObject/UninitializedObjectChecker.cpp b/clang/lib/StaticAnalyzer/Checkers/UninitializedObject/UninitializedObjectChecker.cpp index 5e39cc18f2a..2281d668473 100644 --- a/clang/lib/StaticAnalyzer/Checkers/UninitializedObject/UninitializedObjectChecker.cpp +++ b/clang/lib/StaticAnalyzer/Checkers/UninitializedObject/UninitializedObjectChecker.cpp @@ -286,18 +286,6 @@ bool FindUninitializedFields::isNonUnionUninit(const TypedValueRegion *R, } // Checking bases. - // FIXME: As of now, because of `willObjectBeAnalyzedLater`, objects whose - // type is a descendant of another type will emit warnings for uninitalized - // inherited members. - // This is not the only way to analyze bases of an object -- if we didn't - // filter them out, and didn't analyze the bases, this checker would run for - // each base of the object in order of base initailization and in theory would - // find every uninitalized field. This approach could also make handling - // diamond inheritances more easily. - // - // This rule (that a descendant type's cunstructor is responsible for - // initializing inherited data members) is not obvious, and should it should - // be. const auto *CXXRD = dyn_cast(RD); if (!CXXRD) return ContainsUninitField; -- cgit v1.2.3