[PATCH] D53377: [clang-tidy] Ignore a case where the fix of make_unique check introduces side effect.
Haojian Wu via Phabricator via cfe-commits
cfe-commits at lists.llvm.org
Wed Oct 17 08:13:39 PDT 2018
hokein created this revision.
hokein added a reviewer: alexfh.
Herald added a subscriber: xazax.hun.
Previously, ptr.reset(new char[5]) will be replaced with `p =
make_unique<char[]>(5)`, the fix has side effect -- doing
default initialization, it may cause performace regression (we are
bitten by this rececntly)
The check should be conservative for these cases.
Repository:
rCTE Clang Tools Extra
https://reviews.llvm.org/D53377
Files:
clang-tidy/modernize/MakeSmartPtrCheck.cpp
test/clang-tidy/modernize-make-unique.cpp
Index: test/clang-tidy/modernize-make-unique.cpp
===================================================================
--- test/clang-tidy/modernize-make-unique.cpp
+++ test/clang-tidy/modernize-make-unique.cpp
@@ -403,18 +403,15 @@
// CHECK-FIXES: FFs = std::make_unique<Foo[]>(Num2);
std::unique_ptr<int[]> FI;
- FI.reset(new int[5]);
- // CHECK-MESSAGES: :[[@LINE-1]]:6: warning:
- // CHECK-FIXES: FI = std::make_unique<int[]>(5);
- FI.reset(new int[5]());
+ FI.reset(new int[5]()); // default initialization.
// CHECK-MESSAGES: :[[@LINE-1]]:6: warning:
// CHECK-FIXES: FI = std::make_unique<int[]>(5);
+
+ // The check doesn't give warnings and fixes for cases where the original new
+ // expresion doesn't do any initialization.
+ FI.reset(new int[5]);
FI.reset(new int[Num]);
- // CHECK-MESSAGES: :[[@LINE-1]]:6: warning:
- // CHECK-FIXES: FI = std::make_unique<int[]>(Num);
FI.reset(new int[Num2]);
- // CHECK-MESSAGES: :[[@LINE-1]]:6: warning:
- // CHECK-FIXES: FI = std::make_unique<int[]>(Num2);
}
void aliases() {
Index: clang-tidy/modernize/MakeSmartPtrCheck.cpp
===================================================================
--- clang-tidy/modernize/MakeSmartPtrCheck.cpp
+++ clang-tidy/modernize/MakeSmartPtrCheck.cpp
@@ -121,6 +121,15 @@
if (New->getNumPlacementArgs() != 0)
return;
+ // Be conservative for cases where we construct an array without any
+ // initalization.
+ // For example,
+ // P.reset(new int[5]) // check fix: P = make_unique<int []>(5)
+ //
+ // The fix of the check has side effect, it introduces default initialization
+ // which maybe unexpected and cause performance regression.
+ if (New->isArray() && !New->hasInitializer())
+ return;
if (Construct)
checkConstruct(SM, Result.Context, Construct, Type, New);
else if (Reset)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D53377.170012.patch
Type: text/x-patch
Size: 1841 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20181017/8ada38da/attachment-0001.bin>
More information about the cfe-commits
mailing list