llvm-project

History

Chandler Carruth 38a61d87a5 Teach the standalone Clang CMake bits about the flag to force using an old toolchain to build. The toolchain version is now checked in HandleLLVMOptions. llvm-svn: 199150		2014-01-13 22:22:24 +00:00
..
INPUTS	…
bindings	[libclang/python] Add CompilationDatabase.getAllCompileCommands to the python bindings.	2013-12-20 01:34:00 +00:00
docs	Whoops! Fix major think-o in the first example in the documentation that I edited at 3am.	2014-01-11 02:55:22 +00:00
examples	Don't use PrintFunctionNames.exports on Windows.	2013-12-30 00:05:56 +00:00
include	Updating the attribute declarations to have the correct syntaxes. This means giving a __declspec spelling to: deprecated, naked, noinline, noreturn, and nothrow. uuid has no GNU spelling, so it was switched to __declspec. dllexport and dllimport both are now supported with GNU spellings.	2014-01-13 21:32:48 +00:00
lib	When determining the attribute's parsed kind, pay attention to the syntax used. This fixes bugs where an attribute has differing GNU and Declspec spellings, but they are treated as the same. Eg) __declspec(aligned) when it should be __attribute__((aligned)), and __attribute__((align)) when it should be __declspec(align).	2014-01-13 21:42:39 +00:00
runtime	Only build ARM-specific runtimes if ARM is enabled	2013-12-11 12:01:21 +00:00
test	There is no such thing as __attribute__((align)); that's a __declspec attribute. Fixing these test cases to use the proper spelling for their syntax.	2014-01-13 21:30:03 +00:00
tools	Use -std=gnu89 in tools/c-index-test/CMakeLists.txt	2014-01-08 11:44:42 +00:00
unittests	clang-format: Fix corner case with comment in ctor initializer.	2014-01-13 14:10:04 +00:00
utils	When determining the attribute's parsed kind, pay attention to the syntax used. This fixes bugs where an attribute has differing GNU and Declspec spellings, but they are treated as the same. Eg) __declspec(aligned) when it should be __attribute__((aligned)), and __attribute__((align)) when it should be __declspec(align).	2014-01-13 21:42:39 +00:00
www	Regenerate DR status page.	2013-12-10 08:26:19 +00:00
.arcconfig	…
.clang-format	…
.gitignore	…
CMakeLists.txt	Teach the standalone Clang CMake bits about the flag to force using an	2014-01-13 22:22:24 +00:00
CODE_OWNERS.TXT	Update contact information.	2013-11-15 17:35:53 +00:00
INSTALL.txt	…
LICENSE.TXT	Update the copyright credits -- Happy new year 2014!	2014-01-01 08:27:31 +00:00
Makefile	Define ENABLE_CLANG_EXAMPLES instead of relying on BUILD_EXAMPLES	2014-01-08 13:00:32 +00:00
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.cs.uiuc.edu/mailman/listinfo/cfe-dev

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