llvm-project/clang
Sam McCall ce2b40def1 [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
2019-02-15 07:16:11 +00:00
..
INPUTS
bindings [libclang] Add attribute support for 'convergent'. 2019-02-11 11:00:56 +00:00
cmake [CMake][Fuchsia] Pass -ldl -lpthread LDFLAGS to second stage 2019-02-12 16:24:46 +00:00
docs [HWASAN] Updated HWASAN design document to better portray the chance of missing a bug. 2019-02-13 23:14:54 +00:00
examples Update the file headers across all of the LLVM projects in the monorepo 2019-01-19 08:50:56 +00:00
include Revert "Fix implementation of [temp.local]p4." 2019-02-15 03:06:15 +00:00
lib [Analysis] -Wunreachable-code shouldn't fire on the increment of a foreach loop 2019-02-15 07:16:11 +00:00
runtime [CMake] External compiler-rt-configure requires LLVMTestingSupport when including tests 2019-02-01 15:35:25 +00:00
test [Analysis] -Wunreachable-code shouldn't fire on the increment of a foreach loop 2019-02-15 07:16:11 +00:00
tools [tools] Fix python DeprecationWarning: invalid escape sequence 2019-02-11 15:03:17 +00:00
unittests [clang][FileManager] fillRealPathName even if we aren't opening the file 2019-02-14 23:02:35 +00:00
utils Use llvm::is_contained. NFC 2019-02-10 05:54:57 +00:00
www [analyzer] Document RetainCountChecker behavior and annotations 2019-02-05 22:27:10 +00:00
.arcconfig
.clang-format
.clang-tidy Disable tidy checks with too many hits 2019-02-01 11:20:13 +00:00
.gitignore Adjust documentation for git migration. 2019-01-29 16:37:27 +00:00
CMakeLists.txt This reverts commit 1440a848a635849b97f7a5cfa0ecc40d37451f5b. 2019-02-09 00:46:12 +00:00
CODE_OWNERS.TXT Add myself as code owner for OpenBSD driver 2018-11-30 21:42:34 +00:00
INSTALL.txt
LICENSE.TXT Fix typos throughout the license files that somehow I and my reviewers 2019-01-21 09:52:34 +00:00
ModuleInfo.txt
NOTES.txt PTH-- Remove feature entirely- 2018-12-04 14:34:09 +00:00
README.txt

README.txt

//===----------------------------------------------------------------------===//
// C Language Family Front-end
//===----------------------------------------------------------------------===//

Welcome to Clang.  This is a compiler front-end for the C family of languages
(C, C++, Objective-C, and Objective-C++) which is built as part of the LLVM
compiler infrastructure project.

Unlike many other compiler frontends, Clang is useful for a number of things
beyond just compiling code: we intend for Clang to be host to a number of
different source-level tools.  One example of this is the Clang Static Analyzer.

If you're interested in more (including how to build Clang) it is best to read
the relevant web sites.  Here are some pointers:

Information on Clang:             http://clang.llvm.org/
Building and using Clang:         http://clang.llvm.org/get_started.html
Clang Static Analyzer:            http://clang-analyzer.llvm.org/
Information on the LLVM project:  http://llvm.org/

If you have questions or comments about Clang, a great place to discuss them is
on the Clang development mailing list:
  http://lists.llvm.org/mailman/listinfo/cfe-dev

If you find a bug in Clang, please file it in the LLVM bug tracker:
  http://llvm.org/bugs/