diff options
author | Sam McCall <sam.mccall@gmail.com> | 2019-02-15 07:16:11 +0000 |
---|---|---|
committer | Sam McCall <sam.mccall@gmail.com> | 2019-02-15 07:16:11 +0000 |
commit | ce2b40def1765832ac505033bf24a78fe85d06f9 (patch) | |
tree | 7cce1be8d8b8fe20ace2311f8f4920ce7c4bf0be /lldb/packages/Python/lldbsuite/test/tools/lldb-server/TestGdbRemoteModuleInfo.py | |
parent | 184bd7a0d856086d1ed22a6b53f37c8d39e9a2b0 (diff) | |
download | bcm5719-llvm-ce2b40def1765832ac505033bf24a78fe85d06f9.tar.gz bcm5719-llvm-ce2b40def1765832ac505033bf24a78fe85d06f9.zip |
[Analysis] -Wunreachable-code shouldn't fire on the increment of a foreach loop
Summary:
The idea is that the code here isn't written, so doesn't indicate a bug.
Similar to code expanded from macros.
This means the warning no longer fires on this code:
for (auto C : collection) {
process(C);
return;
}
handleEmptyCollection();
Unclear whether this is more often a bug or not in practice, I think it's a
reasonable idiom in some cases.
Either way, if we want to warn on "loop that doesn't loop", I think it should be
a separate warning, and catch `while(1) break;`
Reviewers: ilya-biryukov, ioeric
Subscribers: cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D58134
llvm-svn: 354102
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/tools/lldb-server/TestGdbRemoteModuleInfo.py')
0 files changed, 0 insertions, 0 deletions