llvm-project/clang
John McCall c07a0c7e48 Change the representation of GNU ?: expressions to use a different expression
class and to bind the shared value using OpaqueValueExpr.  This fixes an
unnoticed problem with deserialization of these expressions where the
deserialized form would lose the vital pointer-equality trait;  or rather,
it fixes it because this patch also does the right thing for deserializing
OVEs.

Change OVEs to not be a "temporary object" in the sense that copy elision is
permitted.

This new representation is not totally unawkward to work with, but I think
that's really part and parcel with the semantics we're modelling here.  In
particular, it's much easier to fix things like the copy elision bug and to
make the CFG look right.

I've tried to update the analyzer to deal with this in at least some          
obvious cases, and I think we get a much better CFG out, but the printing
of OpaqueValueExprs probably needs some work.

llvm-svn: 125744
2011-02-17 10:25:35 +00:00
..
INPUTS
bindings/python python bindings: Add support for different kind of completion chunks 2011-02-05 17:54:10 +00:00
clang.xcodeproj Anger the CMake gods by updating 'clang.xcodeproj'. 2011-02-14 20:09:57 +00:00
docs fix two broken links and some out of date writing, PR9174 2011-02-14 06:42:50 +00:00
examples Fix the clang-wpa example. 2011-02-15 16:54:12 +00:00
include Change the representation of GNU ?: expressions to use a different expression 2011-02-17 10:25:35 +00:00
lib Change the representation of GNU ?: expressions to use a different expression 2011-02-17 10:25:35 +00:00
runtime build/compiler-rt: Fake Clang into using the right assembler to build the ARM 2011-02-11 01:29:49 +00:00
test Change the representation of GNU ?: expressions to use a different expression 2011-02-17 10:25:35 +00:00
tools Change the representation of GNU ?: expressions to use a different expression 2011-02-17 10:25:35 +00:00
unittests Adds a CMake target for the Basic lib's unit tests. Reviewed by 2011-02-16 05:45:20 +00:00
utils Minor fix for clang-completion-mode, from Dve Abrahams 2010-12-14 16:52:29 +00:00
www Update static analyzer build to checker-255. 2011-02-12 03:20:34 +00:00
CMakeLists.txt CMake: Tweak for Visual Studio 10 quirk at clang-standalone build. 2011-02-16 03:07:15 +00:00
INSTALL.txt
LICENSE.TXT
Makefile Add gTest unittests to clang, and write the first one. 2011-02-03 04:51:52 +00:00
ModuleInfo.txt
NOTES.txt A Release-Asserts build is now called a Release build. 2010-07-07 07:49:17 +00:00
README.txt Fix typo (test commit) 2010-06-17 12:39:05 +00:00
TODO.txt Test commit; added blank line to TODO.txt 2011-01-04 19:19:20 +00:00

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/