llvm-project/clang
Vedant Kumar 4b62b5cddd [ubsan] Mark overflow checks with !nosanitize
Sanitizer instrumentation generally needs to be marked with !nosanitize,
but we're not doing this properly for ubsan's overflow checks.

r213291 has more information about why this is needed.

llvm-svn: 302598
2017-05-09 23:34:49 +00:00
..
INPUTS
bindings Add Python 3 support to clang.cindex 2017-04-20 10:11:01 +00:00
cmake Build the Apple-style stage2 with modules 2017-05-09 17:27:03 +00:00
docs docs: Fix Sphinx detection with out-of-tree builds 2017-05-09 01:42:33 +00:00
examples Add LLVMOption to clang-interpreter, corresponding to r291938. 2017-01-14 08:54:05 +00:00
include Don't mark a member as a member specialization until we know we're keeping the specialization. 2017-05-09 23:02:10 +00:00
lib [ubsan] Mark overflow checks with !nosanitize 2017-05-09 23:34:49 +00:00
runtime [sanitizer] Passthrough CMAKE_OSX_DEPLOYMENT_TARGET and CMAKE_OSX_SYSROOT when building compiler-rt from clang/runtime/CMakeLists.txt 2016-12-15 23:20:54 +00:00
test [ubsan] Mark overflow checks with !nosanitize 2017-05-09 23:34:49 +00:00
tools [modules] Round-trip -Werror flag through explicit module build. 2017-05-03 00:28:49 +00:00
unittests clang-format: [JS] Don't indent JavaScript IIFEs. 2017-05-09 20:04:09 +00:00
utils utils: Silence -Wpedantic warning 2017-05-01 00:26:59 +00:00
www [Sema] Implement Core 2094: Trivial copy/move constructor for class with volatile member 2017-05-09 22:21:24 +00:00
.arcconfig
.clang-format
.clang-tidy
.gitignore
CMakeLists.txt [analyzer] Add new Z3 constraint manager backend 2017-04-04 19:52:25 +00:00
CODE_OWNERS.TXT
INSTALL.txt
LICENSE.TXT
ModuleInfo.txt
NOTES.txt
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/