Changes in cxx-uninitialized-object.cpp

f40c18b6 - [analyzer] PR41753: Include complex integer types in NonLoc::isCompoundType

Sat, 18 May 2019 12:34:08 +0000

[analyzer] PR41753: Include complex integer types in NonLoc::isCompoundTypehttps://bugs.llvm.org/show_bug.cgi?id=41753Differential Revision: https://reviews.llvm.org/D61570llvm-svn: 361099 List of files: /llvm-project-15.0.7/clang/test/Analysis/cxx-uninitialized-object.cpp

aa9d2623 - [analyzer][UninitializedObjectChecker] PR41741: Regard all scalar types as primitive.

Sun, 05 May 2019 19:42:33 +0000

[analyzer][UninitializedObjectChecker] PR41741: Regard all scalar types as primitive.https://bugs.llvm.org/show_bug.cgi?id=41741Pretty much the same as D61246 and D61106, this time for __complex__ types. Uponfurther investigation, I realized that we should regard all typesType::isScalarType returns true for as primitive, so I merged isMemberPointerType(), isBlockPointerType() and isAnyComplexType()` into thatinstead.I also stumbled across yet another bug,https://bugs.llvm.org/show_bug.cgi?id=41753, but it seems to be unrelated tothis checker.Differential Revision: https://reviews.llvm.org/D61569llvm-svn: 359998 List of files: /llvm-project-15.0.7/clang/test/Analysis/cxx-uninitialized-object.cpp

c21ec00d - [analyzer][UninitializedObjectChecker] PR41611: Regard vector types as primitive

Tue, 30 Apr 2019 08:47:56 +0000

[analyzer][UninitializedObjectChecker] PR41611: Regard vector types as primitivehttps://bugs.llvm.org/show_bug.cgi?id=41611Similarly to D61106, the checker ran over an llvm_unreachable for vector types:struct VectorSizeLong { VectorSizeLong() {} __attribute__((__vector_size__(16))) long x;};void __vector_size__LongTest() { VectorSizeLong v;}Since, according to my short research,"The vector_size attribute is only applicable to integral and float scalars,although arrays, pointers, and function return values are allowed in conjunctionwith this construct."[src: https://gcc.gnu.org/onlinedocs/gcc-4.6.1/gcc/Vector-Extensions.html#Vector-Extensions]vector types are safe to regard as primitive.Differential Revision: https://reviews.llvm.org/D61246llvm-svn: 359539 List of files: /llvm-project-15.0.7/clang/test/Analysis/cxx-uninitialized-object.cpp

f46c58e0 - [analyzer][UninitializedObjectChecker] PR41590: Regard _Atomic types as primitive

Thu, 25 Apr 2019 20:00:51 +0000

[analyzer][UninitializedObjectChecker] PR41590: Regard _Atomic types as primitivehttps://bugs.llvm.org/show_bug.cgi?id=41590For the following code snippet, UninitializedObjectChecker crashed:struct MyAtomicInt { _Atomic(int) x; MyAtomicInt() {}};void entry() { MyAtomicInt b;}The problem was that _Atomic types were not regular records, unions,dereferencable or primitive, making the checker hit the llvm_unreachable atlib/StaticAnalyzer/Checkers/UninitializedObject/UninitializedObjectChecker.cpp:347.The solution is to regard these types as primitive as well. The test case showsthat with this addition, not only are we able to get rid of the crash, but wecan identify x as uninitialized.Differential Revision: https://reviews.llvm.org/D61106llvm-svn: 359230 List of files: /llvm-project-15.0.7/clang/test/Analysis/cxx-uninitialized-object.cpp

85e0ff75 - [analyzer] Move UninitializedObjectChecker out of alpha

Fri, 19 Apr 2019 23:33:50 +0000

[analyzer] Move UninitializedObjectChecker out of alphaMoved UninitializedObjectChecker from the 'alpha.cplusplus' to the'optin.cplusplus' package.Differential Revision: https://reviews.llvm.org/D58573llvm-svn: 358797 List of files: /llvm-project-15.0.7/clang/test/Analysis/cxx-uninitialized-object.cpp

3d90e7e8 - Revert "[analyzer] Toning down invalidation a bit".

Wed, 03 Apr 2019 18:21:16 +0000

Revert "[analyzer] Toning down invalidation a bit".This reverts commit r352473.The overall idea is great, but it seems to cause unintented consequenceswhen not only Region Store invalidation but also pointer escape mechanismwas accidentally affected.Based on discussions in https://reviews.llvm.org/D58121#1452483and https://reviews.llvm.org/D57230#1434161Differential Revision: https://reviews.llvm.org/D57230llvm-svn: 357620 List of files: /llvm-project-15.0.7/clang/test/Analysis/cxx-uninitialized-object.cpp

f41e3d08 - [analyzer] Toning down invalidation a bit

Tue, 29 Jan 2019 10:27:14 +0000

[analyzer] Toning down invalidation a bitWhen a function takes the address of a field the analyzer will no longerassume that the function will change other fields of the enclosing structs.Differential Revision: https://reviews.llvm.org/D57230llvm-svn: 352473 List of files: /llvm-project-15.0.7/clang/test/Analysis/cxx-uninitialized-object.cpp

f0dd1016 - [analyzer][UninitializedObjectChecker] Fixed dereferencing

Fri, 14 Sep 2018 08:58:21 +0000

[analyzer][UninitializedObjectChecker] Fixed dereferencingiThis patch aims to fix derefencing, which has been debated for months now.Instead of working with SVals, the function now relies on TypedValueRegion.Differential Revision: https://reviews.llvm.org/D51057llvm-svn: 342213 List of files: /llvm-project-15.0.7/clang/test/Analysis/cxx-uninitialized-object.cpp

015b0595 - [analyzer][UninitializedObjectChecker] Refactoring p4.: Wrap FieldRegions and reduce weight on FieldChainInfo

Mon, 13 Aug 2018 18:43:08 +0000

[analyzer][UninitializedObjectChecker] Refactoring p4.: Wrap FieldRegions and reduce weight on FieldChainInfoBefore this patch, FieldChainInfo used a spaghetti: it took care of way too many cases,even though it was always meant as a lightweight wrapper aroundImmutableList.This problem is solved by introducing a lightweight polymorphic wrapper around constFieldRegion *, FieldNode. It is an interface that abstracts away special cases likepointers/references, objects that need to be casted to another type for a proper notemessages.Changes to FieldChainInfo: * Now wraps ImmutableList. * Any pointer/reference related fields and methods were removed * Got a new add method. This replaces it's former constructors as a way to create a new FieldChainInfo objects with a new element.Changes to FindUninitializedField: * In order not to deal with dynamic memory management, when an uninitialized field is found, the note message for it is constructed and is stored instead of a FieldChainInfo object. (see doc around addFieldToUninits).Some of the test files are changed too, from now on uninitialized pointees of referencesalways print "uninitialized pointee" instead of "uninitialized field" (which should'vereally been like this from the beginning).I also updated every comment according to these changes.Differential Revision: https://reviews.llvm.org/D50506llvm-svn: 339599 List of files: /llvm-project-15.0.7/clang/test/Analysis/cxx-uninitialized-object.cpp

0735cfbd - [analyzer][UninitializedObjectChecker] Fixed a false negative by no longer filtering out certain constructor calls

Wed, 08 Aug 2018 12:23:02 +0000

[analyzer][UninitializedObjectChecker] Fixed a false negative by no longer filtering out certain constructor callsAs of now, all constructor calls are ignored that are being calledby a constructor. The point of this was not to analyze the fieldsof an object, so an uninitialized field wouldn't be reportedmultiple times.This however introduced false negatives when the two constructorswere in no relation to one another -- see the test file for a neatexample for this with singletons. This patch aims so fix this issue.Differential Revision: https://reviews.llvm.org/D48436llvm-svn: 339237 List of files: /llvm-project-15.0.7/clang/test/Analysis/cxx-uninitialized-object.cpp

a3f7b587 - [analyzer][UninitializedObjectChecker] New flag to turn off dereferencing

Tue, 07 Aug 2018 12:55:26 +0000

[analyzer][UninitializedObjectChecker] New flag to turn off dereferencingEven for a checker being in alpha, some reports about pointees held so littlevalue to the user that it's safer to disable pointer/reference chasing for now.It can be enabled with a new flag, in which case checker should function as ithas always been. This can be set with `CheckPointeeInitialization`.Differential Revision: https://reviews.llvm.org/D49438llvm-svn: 339135 List of files: /llvm-project-15.0.7/clang/test/Analysis/cxx-uninitialized-object.cpp

8c119098 - [analyzer][UninitializedObjectChecker] Fixed captured lambda variable name

Fri, 13 Jul 2018 12:54:47 +0000

[analyzer][UninitializedObjectChecker] Fixed captured lambda variable nameDifferential Revision: https://reviews.llvm.org/D48291llvm-svn: 336995 List of files: /llvm-project-15.0.7/clang/test/Analysis/cxx-uninitialized-object.cpp

30f08656 - [analyzer] Checker for uninitialized C++ objects

Mon, 18 Jun 2018 11:50:17 +0000

[analyzer] Checker for uninitialized C++ objectsThis checker analyzes C++ constructor calls, and reports uninitialized fields.Due to the nature of this problem (uninitialized fields after an objectconstruction), this checker doesn't search for bugs, but rather is a tool toenforce a specific programming model where every field needs to be initialized.This checker lands in alpha for now, and a number of followup patches will bemade to reduce false negatives and to make it easier for the user to understandwhat rules the checker relies on, eg. whether a derived class' constructor isresponsible for initializing inherited data members or whether it should behandled in the base class' constructor.Differential Revision: https://reviews.llvm.org/D45532llvm-svn: 334935 List of files: /llvm-project-15.0.7/clang/test/Analysis/cxx-uninitialized-object.cpp