llvm-svn: 66689

llvm-svn: 66688

llvm-svn: 66687

This fixes fallout from recent PIC/delibtoolize changes and unbreaks
build on cygming.

llvm-svn: 66686

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

llvm-svn: 66685

llvm-svn: 66684

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

llvm-svn: 66663

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: 66660

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: 66653

llvm-svn: 66652

linkage: this linkage type only applies to declarations,
but ODR is only relevant to globals with definitions.

llvm-svn: 66650

llvm-svn: 66649

variety.  For example, an i64 div might turn into a call to __divdi3 during
legalization.

llvm-svn: 66646

llvm-svn: 66645

llvm-svn: 66643

llvm-svn: 66642

alignment of the generated constant pool entry to the
desired alignment of a type.  If we don't do this, we end up
trying to do movsd from 4-byte alignment memory.  This fixes
450.soplex and 456.hmmer.

llvm-svn: 66641

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