llvm-capstone/clang
Bob Wilson 5f4e3a780f Add bigger method type encodings to protocol objects. <rdar://problem/10492418>
The new metadata are method @encode strings with additional data.

1. Each Objective-C object is marked with its class name and protocol names.
The same is done for property @encode already.

2. Each block object is marked with its function prototype's @encoding. For
example, a method parameter that is a block object that itself returns void
and takes an int would look like:
    @?<v@?i>

These new method @encode strings are stored in a single array pointed to by structs protocol_t and objc_protocol_ext.

Patch provided by Greg Parker!

llvm-svn: 145469
2011-11-30 01:57:58 +00:00
..
bindings/python
docs Add Clang release notes for OpenCL C support. 2011-11-29 02:03:07 +00:00
examples Update signature of HandleTopLevelDecl. 2011-11-19 19:22:13 +00:00
include Add bigger method type encodings to protocol objects. <rdar://problem/10492418> 2011-11-30 01:57:58 +00:00
INPUTS
lib Add bigger method type encodings to protocol objects. <rdar://problem/10492418> 2011-11-30 01:57:58 +00:00
runtime Use libcxx makefile's do-installhdrs target. <rdar://problem/10397739> 2011-11-27 06:13:25 +00:00
test Make sure that forward declarations are marked as such in the debug info 2011-11-29 23:57:40 +00:00
tools [libclang] Do the ConcurrencyCheck at the beginning of clang_findReferencesInFile. 2011-11-29 23:21:50 +00:00
unittests
utils Add support for pretty-printing attributes, from Richard Membarth! 2011-11-19 19:22:57 +00:00
www Tweak the guidelines for when one should send patches to cfe-commits vs. cfe-dev 2011-11-19 19:14:26 +00:00
.gitignore
CMakeLists.txt
INSTALL.txt
LICENSE.TXT
Makefile
ModuleInfo.txt
NOTES.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/