llvm-project/clang
Reid Kleckner 400a64e81b Don't print end-of-directive tokens in -E output
This comes up when pre-processing standalone .s files containing
hash-prefixed comments. The pre-processor should skip the unknown
directive and not emit an extra newline as we were doing.

Fixes PR34950

llvm-svn: 315953
2017-10-16 23:07:15 +00:00
..
INPUTS
bindings bindings: expose Linkage to the python bindings 2017-09-22 18:35:09 +00:00
cmake [clang-fuzzer] Build with newer protobuf-mutator. 2017-10-11 20:45:10 +00:00
docs [Sema] Re-land: Diagnose tautological comparison with type's min/max values 2017-10-15 20:13:17 +00:00
examples
include Remove AnyX86Interrupt documentation 2017-10-16 20:44:14 +00:00
lib Don't print end-of-directive tokens in -E output 2017-10-16 23:07:15 +00:00
runtime Allow building libFuzzer tests in two-stage compiler-rt build. 2017-10-13 23:50:53 +00:00
test Don't print end-of-directive tokens in -E output 2017-10-16 23:07:15 +00:00
tools [refactor] allow the use of refactoring diagnostics 2017-10-16 18:28:26 +00:00
unittests [refactor] allow the use of refactoring diagnostics 2017-10-16 18:28:26 +00:00
utils Replace usage of std::stringstream with raw_string_ostream 2017-10-16 22:47:26 +00:00
www Typos in tutorial 2017-10-13 00:31:07 +00:00
.arcconfig
.clang-format
.clang-tidy
.gitignore
CMakeLists.txt Don't search libxml2 if using msan. LLVM already has similar check. 2017-09-02 03:53:42 +00:00
CODE_OWNERS.TXT
INSTALL.txt
LICENSE.TXT
ModuleInfo.txt
NOTES.txt
README.txt Test commit access in clang. 2017-09-03 15:29:38 +00:00

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/