1662184 bytes (~10%)

llvm-svn: 65551

the symbol for the root meta-data.

llvm-svn: 65548

This was a fairly recent regression.

llvm-svn: 65547

llvm-svn: 65544

llvm-svn: 65543

substantially happier on some versions of Mac OS/X.

llvm-svn: 65542

llvm-svn: 65540

For scan-build based analyses, use the '-analyzer-eargely-assume' setting by default (turning it on to test how it impacts users).

llvm-svn: 65535

llvm-svn: 65534

llvm-svn: 65533

The code for looking up local/private method in Sema::ActOnInstanceMessage() was not handling categories properly. Sema::ActOnClassMessage() didn't have this bug.
Created a helper with the correct logic and changed both methods to use it.

llvm-svn: 65532

llvm-svn: 65530

llvm-svn: 65529

Also changed ObjCInterfaceDecl::lookupClassMethod() to look through a categories protocols.

Test/patch submitted by Jean-Daniel Dupas (thanks!).

llvm-svn: 65526

pretty sure we want to keep constant expression verification outside of 
Evaluate. Because of that, the short-circuit evaluation doesn't 
generally make sense, and the comma warning doesn't make sense in its 
current form.

llvm-svn: 65525

is a rather big change, but I think this is the direction we want to go; 
the code is significantly shorter now, and it doesn't duplicate Evaluate 
code.  There shouldn't be any visible changes as far as I know.

There has been some movement towards putting ICE handling into 
Evaluate (for example, VerifyIntegerConstantExpression uses Evaluate 
instead of isICE).  This patch is sort of the opposite of the approach, 
making ICE handling work without Evaluate being aware of it. I think 
this approach is better because it separates the code that does the 
constant evaluation from code that's calculating a rather 
arbitrary predicate.

The one thing I don't really like about this patch is that 
the handling of commas in C99 complicates it signficantly. (Seriously, 
what was the standards committee thinking when they wrote that 
part?) I think I've come up with a decent approach, but it doesn't feel
ideal.  I might add some way to check for evaluated commas from Evaluate 
in a subsequent patch; that said, it might not be worth bothering.

llvm-svn: 65524

llvm-svn: 65523

Don't ask me, how does this makefile-horribleness even work ;)

llvm-svn: 65522

llvm-svn: 65521

llvm-svn: 65520

llvm-svn: 65519

with the rest of the parallel directories.

Build lto when possible on all platforms. Make gold to explicitly depend on
libLTO.

llvm-svn: 65518

llvm-svn: 65517

llvm-svn: 65512

Next step: making them more coherent.

llvm-svn: 65511

 - <rdar://problem/6622451> Bad x86_64 code gen for message call taking one argument.

llvm-svn: 65510

conditional branch predecessors.

llvm-svn: 65509

llvm-svn: 65508

llvm-svn: 65507

llvm-svn: 65504

llvm-svn: 65503

anymore.  If we want to reuse bits and pieces to add strict checking for 
constant initializers, we can dig them out of SVN history; the existing 
code won't be useful as-is.

llvm-svn: 65502

llvm-svn: 65501

variable declarations where applicable.  Also, a few fixes to 
TryToFixInvalidVariablyModifiedType for issues that this exposed.

llvm-svn: 65500

ADDS{D|S}rr_Int and MULS{D|S}rr_Int are not commutable. The users of these intrinsics expect the high bits will not be modified.

llvm-svn: 65499

llvm-svn: 65498

If an available register falls through to a succ block, unset the last kill. Sorry, it's impossible to reduce a sensible test case. It basically requires the moon and stars to align in order to cause a failure.

llvm-svn: 65497

llvm-svn: 65496

llvm-svn: 65493

llvm-svn: 65489