Implicit conversions from arrays can also be conversions to references (will add a test case shortly).

llvm-svn: 58110

Issue warnings about owned objects returned from a method that does not match the established Cocoa naming conventions.

llvm-svn: 58108

Added method "getSelfRegion" to Store.  This method returns the region associated with the "this" or "self" object (C++ and Objective-C respectively).

llvm-svn: 58107

llvm-svn: 58106

The Decl of an array region can be VarDecl or FieldDecl. Handle this in RegionStoreManager::ArrayToPointer().

llvm-svn: 58086

the array initialization code into a function.

llvm-svn: 58083

llvm-svn: 58077

llvm-svn: 58074

llvm-svn: 58073

llvm-svn: 58070

llvm-svn: 58061

llvm-svn: 58058

llvm-svn: 58056

llvm-svn: 58030

llvm-svn: 58028

Disable warning about potential leaks of returned values until we test it a little more (lots of noise).

llvm-svn: 58021

Warn about potentially leaked objects that are returned from methods whose names do not follow the Cocoa Memory Management guidelines.

llvm-svn: 58012

Enhance reference-count checker to correctly identify CG "release" functions.  This fixes <rdar://problem/6303488>.

llvm-svn: 57997

llvm-svn: 57977

llvm-svn: 57964

llvm-svn: 57963

When conjuring symbols for compound assignments, use the promoted type to determine if the symbolic value as a "loc::" or "nonloc::" value.

llvm-svn: 57917

llvm-svn: 57910

llvm-svn: 57909

Handle [NSAutoreleasePool addObject:] (an alternative way to add objects to the current autorelease pool).

Added initial code for tracking stack of autorelease pools.

llvm-svn: 57908

GRExprEngine::VisitCast() so that other parts of the analyzer can be ignorant.
When we cast "array of type T" to "pointer to T", we get the loc::MemRegionVal
corresponding to the array variable. This is sufficient for BasicStore, but not
for RegionStore. RegionStore should get the element region for the first array
element in the cast. So next comes to the revamping of transfer functions for
different store model.

llvm-svn: 57897

llvm-svn: 57896

  RValues.h/cpp => SVals.h/cpp

llvm-svn: 57893

initialized to UndefinedVal.

llvm-svn: 57892

llvm-svn: 57891

Further improve path-sensitivity with divide-by-zero checking by assuming that a denominator cannot be zero even when the result of an '/' or '%' expression is unknown.

llvm-svn: 57855

Used conjured symbols to recover path-sensitivity when the result of a compound assignment is UnknownVal().

llvm-svn: 57851

llvm-svn: 57777

Generalize VisitLValue: not only can CallExprs and ObjCMessageExprs return aggregate temporaries, so can many other expressions.

llvm-svn: 57761

Function calls and ObjC message expressions can be used in a lvalue context if they return a structure.  E.g  foo().x == 1.  We don't really support, however, such temporaries yet in the environment or the store.

llvm-svn: 57760

retain/release checker: Check if a tracked value escapes if we also try binding it to the store and the store doesn't support that binding (i.e., it cannot track it).  This has the nice feature that the checker will automatically get more powerful if we use a more powerful store model.

llvm-svn: 57755

Use "VisitLValue" when processing the base for "x.f" field accesses, and "Visit" when processing the base for "x->f" field accesses.

llvm-svn: 57754

Hack: have BasicStore::getLValueElement return the "Base" lvalue.  This restores null dereference checking with array accesses.

BasicStore::RemoveDeadBindings: handle regions besides VarRegions (we now have FieldRegions).

llvm-svn: 57741

When conjuring symbols to recover path-sensitivity, don't conjure symbols that represent an entire struct.  We need to implement struct temporaries as an actual "region", and then bind symbols to the FieldRegion of those temporaries.

llvm-svn: 57739

Enhance "Assumption" logic in BasicConstraintManager when reasoning about regions and symbolic regions.  When assuming whether or not a location is non-null, walk up the region hierarchy until we hit a symbolic region (and test it for null).  This may not be the end all solution, as the notion of what a "symbolic region" is really belongs in the specific subclass of StoreManager.

llvm-svn: 57730