NameDateSize

..21-Nov-20124 KiB

.gitignore21-Nov-20121.3 KiB

Android.mk21-Nov-2012603

bindings/21-Nov-20124 KiB

clang-host-build.mk21-Nov-20121,007

clang-tblgen-rules.mk21-Nov-201210.4 KiB

clang-version-inc.mk21-Nov-20121.5 KiB

clang.mk21-Nov-2012387

CMakeLists.txt21-Nov-20129.8 KiB

docs/21-Nov-20124 KiB

examples/21-Nov-20124 KiB

gen_diff.sh21-Nov-20121.1 KiB

include/21-Nov-20124 KiB

INPUTS/21-Nov-20124 KiB

INSTALL.txt21-Nov-20122.1 KiB

lib/21-Nov-20124 KiB

LICENSE.TXT21-Nov-20122.7 KiB

Makefile21-Nov-20122.8 KiB

MODULE_LICENSE_BSD_LIKE21-Nov-20120

ModuleInfo.txt21-Nov-201296

NOTES.txt21-Nov-20124.4 KiB

NOTICE21-Nov-20122.7 KiB

README.android21-Nov-20122.5 KiB

README.txt21-Nov-20121.2 KiB

runtime/21-Nov-20124 KiB

test/21-Nov-20124 KiB

tools/21-Nov-20124 KiB

unittests/21-Nov-20124 KiB

utils/21-Nov-20124 KiB

www/21-Nov-20124 KiB

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* For Ice Cream Sandwich MR2: Synced to upstream r146715
21* For Jellybean: Synced to upstream r155088
22* For Jellybean MR1: Synced to upstream r162325.
23
24* Recent downstreaming on 2012/8/23: Synced to r162325 (srhines for merge questions)
25* Recent downstreaming on 2012/8/3: Synced to r160673 (sliao for merge questions)
26* Recent downstreaming on 2012/4/24: Synced to r155088 (sliao for merge questions)
27* Recent downstreaming on 2012/3/24: Synced to r153220 (sliao & srhines for merge questions)
28* Recent downstreaming on 2012/3/5: Synced to r152062 (srhines & sliao for merge questions)
29* Recent downstreaming on 2011/12/17: Synced to r146715 (loganchien & sliao for merge questions)
30* Recent downstreaming on 2011/11/26: Synced to r145117 (loganchien & sliao for merge questions)
31* Recent downstreaming on 2011/11/17: Synced to r144605 (loganchien & sliao for merge questions)
32* Recent downstreaming on 2011/11/14: Synced to r144355 (srhines for merge questions)
33* Recent downstreaming on 2011/10/22: Synced to r142531 (sliao & loganchien for merge questions)
34* Recent downstreaming on 2011/7/21:  Synced to r135574 (sliao & loganchien for merge questions)
35* Recent downstreaming on 2011/7/18:  Synced to r135359 (sliao for merge questions)
36* Recent downstreaming on 2011/7/2:   Synced to r134305 (sliao for merge questions)
37* Recent downstreaming on 2011/6/30:  Synced to r133721 (sliao for merge questions)
38* Recent downstreaming on 2011/6/22:  Synced to r133163 (sliao for merge questions)
39* Recent downstreaming on 2011/4/8:   Synced to r129173 (sliao for merge questions)
40* Recent downstreaming on 2011/3/11:  Synced from r119349 to r127120 (sliao for merge questions)
41
42* We add Android's *.mk files that are specific to Android's build system.
43
44* Changes for enabling both host and device builds.
45
46

README.txt

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