replica
/
hanchenye-llvm-project
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
hanchenye-llvm-project/clang
History
Argyrios Kyrtzidis b6210dff97 [Preprocessor/Modules] Separate the macro directives kinds into their own MacroDirective's subclasses. 
For each macro directive (define, undefine, visibility) have a separate object that gets chained
to the macro directive history. This has several benefits:

-No need to mutate a MacroDirective when there is a undefine/visibility directive. Stuff like
 PPMutationListener become unnecessary.
-No need to keep extra source locations for the undef/visibility locations for the define directive object
 (which is the majority of the directives)
-Much easier to hide/unhide a section in the macro directive history.
-Easier to track the effects of the directives across different submodules.

llvm-svn: 178037
 		2013-03-26 17:17:01 +00:00
..
INPUTS Revert 'Fix a typo 'iff' => 'if''. iff is an abreviation of if and only if. See: http://en.wikipedia.org/wiki/If_and_only_if Commit 164766 2012-09-27 10:16:10 +00:00
bindings cindex.py: Handle NULL pointers when parsing translation units 2013-03-19 15:30:48 +00:00
docs <rdar://problem/13434605> Periodically prune the module cache so that it does not grow forever. 2013-03-25 21:19:16 +00:00
examples The IRReader header is now part of its own library. Update the include 2013-03-26 02:25:54 +00:00
include [Preprocessor/Modules] Separate the macro directives kinds into their own MacroDirective's subclasses. 2013-03-26 17:17:01 +00:00
lib [Preprocessor/Modules] Separate the macro directives kinds into their own MacroDirective's subclasses. 2013-03-26 17:17:01 +00:00
runtime Split ubsan runtime into three pieces (clang part): 2013-03-20 23:49:07 +00:00
test [ms-cxxabi] Mangle vector types 2013-03-26 16:56:59 +00:00
tools [Preprocessor/Modules] Separate the macro directives kinds into their own MacroDirective's subclasses. 2013-03-26 17:17:01 +00:00
unittests Better fix for r177725. 2013-03-22 16:55:40 +00:00
utils [analyzer] Adds cplusplus.NewDelete checker that check for memory leaks, double free, and use-after-free problems of memory managed by new/delete. 2013-03-25 01:35:45 +00:00
www Add a linebreak. Linebreaks are cool. 2013-03-18 21:57:52 +00:00
.arcconfig Add .arcconfig to the repository. Useful if someone wants to use phabricator's command line tool. 2012-12-01 12:08:08 +00:00
.gitignore Reverted unintendedly-committed file. 2013-01-31 19:05:31 +00:00
CMakeLists.txt CMake: -Wno-nested-anon-types for Clang. 2013-03-02 00:49:47 +00:00
CODE_OWNERS.TXT Duplicate some common owners between Clang and LLVM. 2012-11-27 00:48:12 +00:00
INSTALL.txt Minor tweak to install docs 2013-02-05 22:01:16 +00:00
LICENSE.TXT Update the copyright coredits -- Happy new year 2013! 2013-01-01 10:00:19 +00:00
Makefile The top-level clang Makefile is #included into other Makefiles. (sigh) So we 2012-10-03 08:39:19 +00:00
ModuleInfo.txt
…
NOTES.txt Remove an uninteresting note 2013-02-05 21:13:55 +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.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/