TypedViewRegion has a valid rvalue type. Also renamed instance variable 'T' to
'LvalueType' to make it unambiguous of its purpose.

This fixes some crashes I was seeing after:

http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20090309/013771.html

This is because 'isBoundable()' is defined in TypedRegion (the parent class) in
terms of the rvalue type (which could be null), while for TypedViewRegion it
should be defined in terms of the lvalue type.

llvm-svn: 66712

llvm-svn: 66710

Work in progress.

llvm-svn: 66707

Make sure that we set the access specifier for an instantiated FieldDecl, and that the aggregate and POD flags for an instantiated class template are updated based on instantiation of a FieldDecl

llvm-svn: 66701

llvm-svn: 66698

llvm-svn: 66696

llvm-svn: 66691

llvm-svn: 66689

for FieldDecls so that the parser and the template instantiation make
use of the same semantic checking module.

llvm-svn: 66685

llvm-svn: 66680

not be consulted for its size expression when operator* was called in the
StmtIterator (this resulted in an assertion failure).

llvm-svn: 66679

template. More importantly, start to sort out the issues regarding
complete types and nested-name-specifiers, especially the question of:
when do we instantiate a class template specialization that occurs to
the left of a '::' in a nested-name-specifier?

llvm-svn: 66662

llvm-svn: 66661

llvm-svn: 66659

llvm-svn: 66658

The ElementRegion's type depends on the array region's rvalue type. If it was
a pointer type, we would get a loc::SymbolVal for '*p'.

llvm-svn: 66656

llvm-svn: 66655

llvm-svn: 66654

llvm-svn: 66652

llvm-svn: 66649

llvm-svn: 66643

offset may be different that the base. Ultimately we need a better solution for
these issues, but this point-by-point fixes are gradually outlining the scope of
the problem.

llvm-svn: 66638

llvm-svn: 66637

llvm-svn: 66636

llvm-svn: 66635

return an unsigned integer for a null pointer value.

llvm-svn: 66630

llvm-svn: 66629

values. Indicating this in 'canReasonAbout' allows GRExprEngine to recover
path-sensitivity in some cases.

llvm-svn: 66628

path-sensitivity, beyond checking to see if the value is "unknown" also check if
the ConstraintManager can handle the SVal. This allows us to recover some
path-sensitivity by actually discarding some information.

llvm-svn: 66627

llvm-svn: 66626

llvm-svn: 66625

a ConstraintManager can usefully reason about the given SVal.

llvm-svn: 66624

deletes all registered BugTypes from BugReporter, and thus we need to display
the graph first.

llvm-svn: 66623

llvm-svn: 66622

llvm-svn: 66621

llvm-svn: 66620

with "clang t.i s.i" where the .i files contain line markers.
rdar://6667812

llvm-svn: 66619

llvm-svn: 66618

Remove space-break that interrupts one string literal.  This is fine in C, but not in TableGen files.

llvm-svn: 66616

Work in progress.

llvm-svn: 66615