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

llvm-svn: 63926

llvm-svn: 63925

llvm-svn: 63924

llvm-svn: 63922

llvm-svn: 63921

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

implementing PR3492: #include failures should be a fatal error

llvm-svn: 63915

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

llvm-svn: 63903

  - <rdar://problem/6551577> [ccc] require -x with -

llvm-svn: 63901

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

llvm-svn: 63897

llvm-svn: 63896

llvm-svn: 63895

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

llvm-svn: 63872

the documentation to the contrary).

llvm-svn: 63871

llvm-svn: 63869

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

scalar/complex/aggregate cases.
 - Currently disabled for x86_64, triggering a misoptimization
   (PR3489).

llvm-svn: 63864

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