en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Analysis/NewDelete-atomics.cpp#ff1fc21e [analyzer] Suppress more MallocChecker positives in smart pointer destructors.r326249 wasn't quite enough because we often run out of inlining stack depthlimit and for that reason fail to see the atomics we're looking for.Add a more straightforward false positive suppression that is based on the nameof the class. I.e. if we're releasing a pointer in a destructor of a "somethingshared/intrusive/reference/counting something ptr/pointer something", then anyuse-after-free or double-free that occurs later would likely be a falsepositive.rdar://problem/38013606Differential Revision: https://reviews.llvm.org/D44281llvm-svn: 328066 List of files: /llvm-project-15.0.7/clang/test/Analysis/NewDelete-atomics.cpp Wed, 21 Mar 2018 00:49:47 +0000 Artem Dergachev <artem.dergachev@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Analysis/NewDelete-atomics.cpp#5337efc6 [analyzer] MallocChecker: Suppress false positives in shared pointers.Throw away MallocChecker warnings that occur after releasing a pointer within adestructor (or its callees) after performing C11 atomic fetch_add or fetch_subwithin that destructor (or its callees).This is an indication that the destructor's class is likely areference-counting pointer. The analyzer is not able to understand that theoriginal reference count is usually large enough to avoid most use-after-frees.Even when the smart pointer is a local variable, we still have these falsepositives that this patch suppresses, because the analyzer doesn't currentlysupport atomics well enough.Differential Revision: https://reviews.llvm.org/D43791llvm-svn: 326249 List of files: /llvm-project-15.0.7/clang/test/Analysis/NewDelete-atomics.cpp Tue, 27 Feb 2018 21:19:33 +0000 Artem Dergachev <artem.dergachev@gmail.com>