Douglas Gregor b92a1565c3 Implement the lvalue-to-rvalue conversion where needed. The ... lvalue-to-rvalue conversion adjusts lvalues of qualified, non-class type to rvalue expressions of the unqualified variant of that type. For example, given: const int i; (void)(i + 17); the lvalue-to-rvalue conversion for the subexpression "i" will turn it from an lvalue expression (a DeclRefExpr) with type 'const int' into an rvalue expression with type 'int'. Both C and C++ mandate this conversion, and somehow we've slid through without implementing it. We now have both DefaultFunctionArrayConversion and DefaultFunctionArrayLvalueConversion, and which gets used depends on whether we do the lvalue-to-rvalue conversion or not. Generally, we do the lvalue-to-rvalue conversion, but there are a few notable exceptions: - the left-hand side of a '.' operator - the left-hand side of an assignment - a C++ throw expression - a subscript expression that's subscripting a vector Making this change exposed two issues with blocks: - we were deducing const-qualified return types of non-class type from a block return, which doesn't fit well - we weren't always setting the known return type of a block when it was provided with the ^return-type syntax Fixes the current Clang-on-Clang compile failure and PR6076. llvm-svn: 95167		2010-02-03 00:27:59 +00:00
clang	Implement the lvalue-to-rvalue conversion where needed. The	2010-02-03 00:27:59 +00:00
compiler-rt	add __sync_synchronize. Needed by compiler when emitting thumb1 with -fno-builtin	2010-02-02 21:34:04 +00:00
llvm	make any use of the "O" stream in asmprinter print to	2010-02-03 00:22:02 +00:00