Home | History | Annotate | only in /external/clang
Up to higher level directory
NameDateSize
Android.mk28-Mar-2012558
bindings/28-Mar-2012
clang-host-build.mk28-Mar-2012994
clang-tblgen-rules.mk28-Mar-20127.1K
clang-version-inc.mk28-Mar-20121.5K
clang.mk28-Mar-2012387
CMakeLists.txt28-Mar-20129.5K
docs/28-Mar-2012
examples/28-Mar-2012
gen_diff.sh28-Mar-20121.1K
include/28-Mar-2012
INPUTS/28-Mar-2012
INSTALL.txt28-Mar-20122.1K
lib/28-Mar-2012
LICENSE.TXT28-Mar-20122.7K
Makefile28-Mar-20122.8K
MODULE_LICENSE_BSD_LIKE28-Mar-20120
ModuleInfo.txt28-Mar-201296
NOTES.txt28-Mar-20123.8K
NOTICE28-Mar-20122.7K
README.android28-Mar-20121.6K
README.txt28-Mar-20121.2K
runtime/28-Mar-2012
test/28-Mar-2012
tools/28-Mar-2012
unittests/28-Mar-2012
utils/28-Mar-2012
www/28-Mar-2012

README.android

      1 /*
      2  * README.android describes in high-level the LLVM changes that we cannot push
      3  * upstream to the llvm.org repository:
      4  *  - Changes due to Android's build system.
      5  *  - Changes due to Android's toolchain.
      6  *  - Changes due to the limitations in Android-based consumer electronics.
      7  *
      8  * Some of them are to-dos. If and when they are done, there will no longer be
      9  * merge conflicts with upstream on those parts.
     10  *
     11  * The file contains useful hints when we try to resolve future 3-way merge
     12  * conflicts.
     13  */
     14 
     15 * For Honeycomb: Synced to upstream r112347
     16 * For Honeycomb MR1: Synced to upstream r119349
     17 * For Honeycomb MR2: Synced to upstream r119349
     18 * For Ice Cream Sandwich: Synced to upstream r135574
     19 * For Ice Cream Sandwich MR1: Synced to upstream r142531
     20 
     21 * Recent downstreaming on 2011/10/22: From r135574 to r142531 (sliao & logan for merge questions)
     22 * Recent downstreaming on 2011/7/21: From r135359 to r135574 (sliao & logan for merge questions)
     23 * Recent downstreaming on 2011/7/18: From r134305 to r135359 (sliao for merge questions)
     24 * Recent downstreaming on 2011/7/2: From r133721 to r134305 (sliao for merge questions)
     25 * Recent downstreaming on 2011/6/30: From r133163 to r133721 (sliao for merge questions)
     26 * Recent downstreaming on 2011/6/22: From r129173 to r133163 (sliao for merge questions)
     27 * Recent downstreaming on 2011/4/8: From r127120 to r129173 (sliao for merge questions)
     28 * Recent downstreaming on 2011/3/11: From r119349 to r127120 (sliao for merge questions)
     29 
     30 * We add Android's *.mk files that are specific to Android's build system.
     31 
     32 * Changes for enabling both host and device builds.
     33 
     34

README.txt

      1 //===----------------------------------------------------------------------===//
      2 // C Language Family Front-end
      3 //===----------------------------------------------------------------------===//
      4 
      5 Welcome to Clang.  This is a compiler front-end for the C family of languages
      6 (C, C++, Objective-C, and Objective-C++) which is built as part of the LLVM
      7 compiler infrastructure project.
      8 
      9 Unlike many other compiler frontends, Clang is useful for a number of things
     10 beyond just compiling code: we intend for Clang to be host to a number of
     11 different source level tools.  One example of this is the Clang Static Analyzer.
     12 
     13 If you're interested in more (including how to build Clang) it is best to read
     14 the relevant web sites.  Here are some pointers:
     15 
     16 Information on Clang:              http://clang.llvm.org/
     17 Building and using Clang:          http://clang.llvm.org/get_started.html
     18 Clang Static Analyzer:             http://clang-analyzer.llvm.org/
     19 Information on the LLVM project:   http://llvm.org/
     20 
     21 If you have questions or comments about Clang, a great place to discuss them is
     22 on the Clang development mailing list:
     23   http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
     24 
     25 If you find a bug in Clang, please file it in the LLVM bug tracker:
     26   http://llvm.org/bugs/
     27