llvm-svn: 150715

part of class meta-data.

llvm-svn: 150714

llvm-svn: 150713

llvm-svn: 150712

llvm-svn: 150711

name for dot syntax, e.g., NSObject.class or foo.class. For other
C++-keywords-as-method-names, use message send syntax. Fixes
<rdar://problem/10794452>.

llvm-svn: 150710

Call clobbers are now represented with register mask operands.  The
regmask can easily represent the fact that xmm6 is call-preserved while
ymm6 isn't.  This is automatically computed by TableGen from the
CalleeSavedRegs containing xmm6.

llvm-svn: 150709

The different calling conventions and call-preserved registers are
represented with regmask operands that are added dynamically.

llvm-svn: 150708

completions that don't insert braces. Fixes <rdar://problem/10764168>.

llvm-svn: 150707

llvm-svn: 150706

Also fix the fixit (oh the irony) when it uses CFBridgingRetain/CFBridgingRelease;
they are supposed to be calls with the casted expression as parameter, they should
not be inserted into the cast like the __bridge keywords.

llvm-svn: 150705

dependent attributes on static members of templatized classes.

llvm-svn: 150704

Disable machine copy propagation for now. It's known to be buggy (PR11940) and introduces subtle miscompiles in many places.

llvm-svn: 150703

llvm-svn: 150702

Thread-safety analysis: Disable checking inside constructors, destructors, lock, and unlock functions

llvm-svn: 150701

llvm-svn: 150700

llvm-svn: 150699

For compatibility with gcc, clang will now parse gcc attributes on
function definitions, but issue a warning if the attribute is not a
thread safety attribute.  Warning controlled by -Wgcc-compat.

llvm-svn: 150698

This is in preparation for being able to warn about 'q' and other
non-standard format string features.

It also allows us to print its name correctly.

llvm-svn: 150697

llvm-svn: 150696

Turns out this isn't safe, because the code below depends on LHS and RHS having
the same type.

llvm-svn: 150695

llvm-svn: 150694

I think I did not get the implementation right. As the current implementation
works well, we will just stick with it for now.

llvm-svn: 150691

llvm-svn: 150690

llvm-svn: 150689

This finishes generalized initializer support in Sema.

llvm-svn: 150688

Revert "Revert "Make CXXNewExpr contain only a single initialier, and not hold the used constructor itself.""

This reintroduces commit r150682 with a fix for the Bullet benchmark crash.

llvm-svn: 150685

Revert "Make CXXNewExpr contain only a single initialier, and not hold the used constructor itself."
It leads to a compiler crash in the Bullet benchmark.

This reverts commit r12014.

llvm-svn: 150684

llvm-svn: 150683

Holding the constructor directly makes no sense when list-initialized arrays come into play. The constructor is now held in a CXXConstructExpr, if construction is what is done. The new design can also distinguish properly between list-initialization and direct-initialization, as well as implicit default-initialization constructors and explicit value-initialization constructors. Finally, doing it this way removes redundance from the AST because CXXNewExpr doesn't try to handle both the allocation and the initialization responsibilities.

This breaks the static analysis of new expressions. I've filed PR12014 to track this.

llvm-svn: 150682

llvm-svn: 150679

llvm-svn: 150678

llvm-svn: 150677

llvm-svn: 150676

llvm-svn: 150675

llvm-svn: 150674

llvm-svn: 150673

llvm-svn: 150672

llvm-svn: 150671

llvm-svn: 150670