llvm-svn: 63947

llvm-svn: 63945

llvm-svn: 63942

matching member exists. Thanks to Piotr Rak for reporting the problem!

llvm-svn: 63939

llvm-svn: 63929

for FieldRegion. This enables us to track more values.

Simplify SymbolicRegion::getRValueType(). We assume the symbol always has
pointer type.

llvm-svn: 63928

diffing the output of:
  clang -dM -o - -E -x c foo.c | sort

llvm-svn: 63926

llvm-svn: 63925

llvm-svn: 63920

predefines buffer initialization.

llvm-svn: 63919

Now you too can have a 47 bit long long!

llvm-svn: 63918

llvm-svn: 63917

llvm-svn: 63914

llvm-svn: 63913

Use ASTContext's allocator to deallocate Stmt objects instead of using 'delete'.  This fixes <rdar://problem/6561143>.

llvm-svn: 63905

canonicalize by template parameter depth, index, and name, and the
unnamed version of a template parameter serves as the canonical.

TemplateTypeParmDecl no longer needs to inherit from
TemplateParmPosition, since depth and index information is present
within the type.

llvm-svn: 63899

errors to 'fatal' error severity.

llvm-svn: 63894

Add 'AppendValue' to the list of magic CF function names that cause a tracked object to escape.  Fixes <rdar://problem/6560661>.

llvm-svn: 63891

llvm-svn: 63881

llvm-svn: 63879

llvm-svn: 63878

Also, put Objective-C protocols into their own identifier
namespace. Otherwise, we find protocols when we don't want to in C++
(but not in C).

llvm-svn: 63877

llvm-svn: 63872

the documentation to the contrary).

llvm-svn: 63871

However, the cause still remains: the Decl is linked into the chain of its DeclContext and remains there despite being deleted.

llvm-svn: 63868

This shrinks OwningResult by one pointer. Since it is no longer larger than OwningPtr, merge the two.
This leads to simpler client code and speeds up my benchmark by 2.7%.
For some reason, this exposes a previously hidden bug, causing a regression in SemaCXX/condition.cpp.

llvm-svn: 63867

llvm-svn: 63866

 - No intended functionality change, this is essentially enabling
   direct passing of complex and aggregate values, which no ABI is
   using.

llvm-svn: 63863

value.
 - No functionality change.

llvm-svn: 63859

 - No intended functionality change, all current ABI implementations
   were only using indirect for complex/aggregate types, which were
   being passed indirectly with the Direct ABIInfo kind.

llvm-svn: 63858

 - No (intended) functionality change, the semantic changes are to come.

llvm-svn: 63850

llvm-svn: 63849

llvm-svn: 63848

llvm-svn: 63846

llvm-svn: 63845

do the symblic regions associated with them and we need them to be typed.

Current SymbolicRegion::getRValueType() method is very restricting. It may be
modified when we are more clear about what could be the types of symblic
regions.

BasicConstraintManager::Assume() is changed due to that now SymblicRegion is a
subclass of SubRegion.
 

llvm-svn: 63844

checker. This was previously needed because BugReport objects were previously
allocated on the stack and not owned by BugReporter. Now we can just issue them
on the fly. This change was motivated because we were seeing some weird cases
where some really long paths would get issued for bugs (particularly leaks)
because of some double-caching.

llvm-svn: 63840

Untested, Daniel or Nate please review.

llvm-svn: 63814

llvm-svn: 63813

llvm-svn: 63811