diff options
author | Pavel Labath <pavel@labath.sk> | 2019-11-29 14:44:28 +0100 |
---|---|---|
committer | Pavel Labath <pavel@labath.sk> | 2019-12-09 11:01:50 +0100 |
commit | 385ba6065a9f77b4744274a37c97c536f7250701 (patch) | |
tree | 185308e5b279d1e5271ca161929a377d1888a9d0 /lldb/packages/Python/lldbsuite/test/functionalities/exec/secondprog.cpp | |
parent | 6965f835b476f8e8eb55916cac39be7ffe639866 (diff) | |
download | bcm5719-llvm-385ba6065a9f77b4744274a37c97c536f7250701.tar.gz bcm5719-llvm-385ba6065a9f77b4744274a37c97c536f7250701.zip |
[cmake] Disable GCC 9's -Wredundant-move
Summary:
This new warning (enabled by -Wextra) fires when a std::move is
redundant, as the default compiler behavior would be to select a move
operation anyway (e.g., when returning a local variable). Unlike
-Wpessimizing-move, it has no performance impact -- it just adds noise.
Currently llvm has about 1500 of these warnings. Unfortunately, the
suggested fix -- removing std::move -- does not work because of some
older compilers we still support. Specifically clang<=3.8 will not use a
move operation if an implicit conversion is needed (Core issue 1579). In
code like "A f(ConvertibleToA a) { return a; }" it will prefer a copy,
or fail to compile if a copy is not possible.
This patch disables that warning to get a meaningful signal out of a GCC
9 build.
Reviewers: rnk, aaron.ballman, xbolva00
Subscribers: mgorny, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D70963
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/functionalities/exec/secondprog.cpp')
0 files changed, 0 insertions, 0 deletions