llvm-svn: 62841

 - Curiously, a number of the current translations gcc does appear to
   be useless?

llvm-svn: 62831

llvm-svn: 62830

llvm-svn: 62829

Objective-C declarations!) again. Fixes <rdar://problem/6517155>

llvm-svn: 62826

--assert, --classpath).
 - Requires providing some option parameters to over-ride rendering in
   order to match gcc. There may be a cleaner way to do this (probably
   by introducing a new option type for long JoinedOrSeparate forms).

llvm-svn: 62825

forwarding -s to linker, and was only taking last arg in some cases
when should have been taking all).

llvm-svn: 62824

extension. Addresses clang PR/3371.

llvm-svn: 62823

 - Unlike groups (which gather distinct but related options), aliases
   are for options like '--all-warnings' which are effectively treated
   like some other option ('-Wall') both in the driver logic and when
   passing to tools.

llvm-svn: 62820

llvm-svn: 62819

llvm-svn: 62818

llvm-svn: 62817

For now, return UnknownVal() in RegionStore::getElementsSize() for AnonTypedRegions.  It wasn't really doing the right thing and was crashing on rdar-6442306-1.m.  This fix causes all path-sensitive test cases to pass with RegionStore.

llvm-svn: 62816

load is always aligned.

I verified that the bswap doesn't occur in the assembly code on x86.

llvm-svn: 62815

Add RegionStore support for the implicit object region that 'self' references.  This causes tests 'ObjCProperties.m' and 'refcnt_naming.m' to now pass with RegionStore.

llvm-svn: 62814

initializers, so that we are within the appropriate subobject after
we've processed a multi-designator designation. We're matching GCC and
EDG's behavior on all examples I've found thus far.

*Huge* thanks to Eli Friedman for pointing out my fundamental
misunderstanding of "current object" in the C99 spec.

llvm-svn: 62812

parent wasn't expecting it.

llvm-svn: 62811

llvm-svn: 62808

for the new meta-data.

llvm-svn: 62806

llvm-svn: 62805

llvm-svn: 62804

llvm-svn: 62803

llvm-svn: 62802

llvm-svn: 62801

llvm-svn: 62800

llvm-svn: 62799

llvm-svn: 62798

llvm-svn: 62796

llvm-svn: 62795

llvm-svn: 62785

llvm-svn: 62782

Fix RegionStore::getLValueElement() to handle the case when the base region is not an ElementRegion (also do some cleanups of its core logic).
This gets array-struct.c to work with RegionStore.

llvm-svn: 62781

descriptive.

llvm-svn: 62775

fsyntax-only with PTH by 3%.

llvm-svn: 62774

llvm-svn: 62773

The 'misc-ps.m' test case now passes with RegionStore.  One case needed to be split out into 'misc-ps-basic-store.m' and 'misc-ps-region-store.m' because the behavior was different between the two store models (RegionStore flags an additional valid bug).

llvm-svn: 62772

SymbolReaper::isLive(SymbolRef) now always returns true for SymbolRegionRvalues because these represent the symbolic values for parameters/globals upon entry to the function.  These values are always ;live' because they represent constraints on the context of how the function was called.  This will be useful for both summary generation but is also necessary to get RegionStore's lazy-binding of locations to symbols to work in practice with RemoveDeadBindings.

llvm-svn: 62771

their associated APIs.  We no longer need separate SymbolData objects
for fields, variables, etc.  Instead, we now associated symbols with
the "rvalue" of a MemRegion (i.e., the value stored at that region).
Now we only have two kinds of SymbolData objects: SymbolRegionRValue
and SymbolConjured.

This cleanup also makes the distinction between a SymbolicRegion and a
symbolic value that is a location much clearer.  A SymbolicRegion
represents a chunk of symbolic memory, while a symbolic location is
just a "pointer" with different possible values.  Without any specific
knowledge, a symbolic location resolves (i.e., via a dereference) to a
SymbolicRegion.  In the future, when we do better alias reasoning, a
symbolic location can become an alias for another location, thus
merging the constraints on the referred SymbolicRegion with the other
region.

llvm-svn: 62769

Uncomment the define in Ownership.h to disable the smart pointers.
Disabled, the smart pointers no longer contain a pointer
to the action, and no longer have special destruction or
copying semantics. They are, compiler willing, raw
pointers or ActionResult equivalents.

llvm-svn: 62767

llvm-svn: 62766