diff options
author | Alex Langford <apl@fb.com> | 2019-08-14 01:09:07 +0000 |
---|---|---|
committer | Alex Langford <apl@fb.com> | 2019-08-14 01:09:07 +0000 |
commit | 21872bc9bf374db7f7f340758ac9bf262b892a53 (patch) | |
tree | 2fc20c1c3b3e1c71f66dd5efd55c4fc506199ea8 /lldb/packages/Python/lldbsuite/test/python_api/default-constructor | |
parent | 5ee4d7a859dc2029adb3ff5a30aaed6b0fb816af (diff) | |
download | bcm5719-llvm-21872bc9bf374db7f7f340758ac9bf262b892a53.tar.gz bcm5719-llvm-21872bc9bf374db7f7f340758ac9bf262b892a53.zip |
[analyzer] Don't delete TaintConfig copy constructor
Summary:
Explicitly deleting the copy constructor makes compiling the function
`ento::registerGenericTaintChecker` difficult with some compilers. When we
construct an `llvm::Optional<TaintConfig>`, the optional is constructed with a
const TaintConfig reference which it then uses to invoke the deleted TaintConfig
copy constructor.
I've observered this failing with clang 3.8 on Ubuntu 16.04.
Reviewers: compnerd, Szelethus, boga95, NoQ, alexshap
Subscribers: xazax.hun, baloghadamsoftware, szepet, a.sidorin, mikhail.ramalho, donat.nagy, dkrupp, Charusso, llvm-commits, cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D66192
llvm-svn: 368779
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/default-constructor')
0 files changed, 0 insertions, 0 deletions