llvm-svn: 129202

per PR9577

llvm-svn: 129201

Patch by Dave Zarzycki!

llvm-svn: 129189

to eliminate a divide-by-8. No change in functionality intended.

llvm-svn: 129180

the base offset. No change in functionality intended.

llvm-svn: 129179

llvm-svn: 129178

llvm-svn: 129176

Nom Nom Nom.

Patch by Anton Korobeynikov!

llvm-svn: 129174

llvm-svn: 129173

a block. First part of // rdar://9254348

llvm-svn: 129171

llvm-svn: 129169

llvm-svn: 129167

Start overhauling static analyzer support for C++ constructors.  The inlining support isn't complete, and needs
to be reworked to model CallEnter/CallExit (just like all other calls).  For now, treat constructors mostly
like other function calls, making the analysis of C++ code just a little more useful.

llvm-svn: 129166

llvm-svn: 129164

llvm-svn: 129162

Do not use zero as an upper bound for unbounded array because upper bound zero also indicates one element array. 

llvm-svn: 129157

llvm-svn: 129153

llvm-svn: 129145

This patch authored by Eric Niebler.

Many methods on the Sema class (e.g. ConvertPropertyForRValue) take Expr
pointers as in/out parameters (Expr *&).  This is especially true for the
routines that apply implicit conversions to nodes in-place.  This design is
workable only as long as those conversions cannot fail.  If they are allowed
to fail, they need a way to report their failures.  The typical way of doing
this in clang is to use an ExprResult, which has an extra bit to signal a
valid/invalid state.  Returning ExprResult is de riguour elsewhere in the Sema
interface.  We suggest changing the Expr *& parameters in the Sema interface
to ExprResult &.  This increases interface consistency and maintainability.

This interface change is important for work supporting MS-style C++
properties.  For reasons explained here
<http://lists.cs.uiuc.edu/pipermail/cfe-dev/2011-February/013180.html>,
seemingly trivial operations like rvalue/lvalue conversions that formerly
could not fail now can.  (The reason is that given the semantics of the
feature, getter/setter method lookup cannot happen until the point of use, at
which point it may be found that the method does not exist, or it may have the
wrong type, or overload resolution may fail, or it may be inaccessible.)

llvm-svn: 129143

implement lhs's protocols. // rdar://9091389.
 

llvm-svn: 129142

llvm-svn: 129141

Chris's feedback.

llvm-svn: 129127

definitely have a path leading to them, and possibly have a path leading
to them; reflect that distinction in the warning text emitted.

llvm-svn: 129126

llvm-svn: 129108

llvm-svn: 129103

llvm-svn: 129102

llvm-svn: 129097

llvm-svn: 129095

outputting dwarf-debug-flags.

llvm-svn: 129094

output missing data.

llvm-svn: 129093

llvm-svn: 129091

it.

llvm-svn: 129089

accurately track warning/error counts.

llvm-svn: 129088

llvm-svn: 129086

-Allow removing a line completely if it ends up empty
-Provide more control on what should be removed.

llvm-svn: 129085

Add FullSourceLoc::BeforeThanCompare. a comparison function class, useful for sorting FullSourceLocs.

llvm-svn: 129084

existing CC_PRINT_OPTIONS and CC_PRINT_HEADERS, which can be used to
transparently capture the compiler diagnostics from a build.

llvm-svn: 129082

Change the return type of CodeGenVTables::getVirtualBaseOffsetOffset() to
CharUnits. No change in functionality intended.

llvm-svn: 129072

llvm-svn: 129066

The idea is that you can create a VarDecl with an unknown type, or a
FunctionDecl with an unknown return type, and it will still be valid to
access that object as long as you explicitly cast it at every use.  I'm
still going back and forth about how I want to test this effectively, but
I wanted to go ahead and provide a skeletal implementation for the LLDB
folks' benefit and because it also improves some diagnostic goodness for
placeholder expressions.

llvm-svn: 129065