[PATCH] D102835: [analyzer] Correctly propagate ConstructionContextLayer thru ParenExpr
Tomasz KamiĆski via Phabricator via cfe-commits
cfe-commits at lists.llvm.org
Thu May 20 05:01:03 PDT 2021
tomasz-kaminski-sonarsource added inline comments.
================
Comment at: clang/test/Analysis/NewDelete-checker-test.cpp:41-52
+// RUN: %clang_analyze_cc1 -std=c++17 -fblocks %s \
+// RUN: -verify=expected,newdelete \
+// RUN: -analyzer-checker=core \
+// RUN: -analyzer-checker=cplusplus.NewDelete \
+// RUN: -analyzer-config c++-allocator-inlining=true
+//
+// RUN: %clang_analyze_cc1 -std=c++17 -fblocks -verify %s \
----------------
Szelethus wrote:
> This mail adds some insight into the usage of `c++-allocator-inlining`:
>
> https://lists.llvm.org/pipermail/cfe-dev/2020-February/064754.html
>
> About the code in `MallocChecker` that handles this flag (`NewDelete` is a part of this as well):
>
> > Yes, we should remove the old code for c++-allocator-inlining=false. The worry we've had back then as that in the new mode we've disabled aggressive behavior of MallocChecker in which it reacted to some overloaded operator new invocations but i think this was the right thing to do and also nobody complained; also nothing prevents us from bringing back the old behavior in a much less confusing way.
>
> As a response, D75432 removed all code that handed `c++-allocator-inlinging=false`. So these RUN lines can be removed I think.
I have removed new runs with the c++-allocator-inlinging=true, and checked other files that have duplicated runs, and removed them.
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D102835/new/
https://reviews.llvm.org/D102835
More information about the cfe-commits
mailing list