Use 'opt < %s' instead of just 'opt %s' to ensure that no temporary files are
created.

llvm-svn: 167372

I'm applying it anyway since it seems to be obviously correct.

llvm-svn: 167370

llvm-svn: 167369

llvm-svn: 167366

The operator== method is a synonym for IsExactMatch().  

The essential difference between these two is that IsCompatibleMatch()
will say that armv7 and armv7s are compatible and return true.
IsExactMatch() will say that armv7 and armv7s are not a match.

An armv7s cpu can run either generic armv7 binaries or armv7s binaries
(the latter being tuned for it).  When we're picking the slice of a 
universal Mach-O file to load in an armv7s Target, we need to be able to
first look for an exact cpu subtype match (armv7s == armv7s) and failing
that, looking for a slice with a compatible architecture.

Update ObjectContainerUniversalMachO::GetObjectFile to prefer an exact
match of the cpu type, falling back to a compatible match if necessary.

<rdar://problem/12593515>

llvm-svn: 167365

the ellipsis is shorter than the text it replaces

llvm-svn: 167364

compound statement.

llvm-svn: 167363

checking against a blacklist.

llvm-svn: 167362

llvm-svn: 167361

llvm-svn: 167360

llvm-svn: 167359

llvm-svn: 167358

llvm-svn: 167357

is that the unit test doesn't have IntTy equal to APInt, instead it uses a class
derived from APInt.  When, as in these lines, an IntTy& reference is returned
but is assigned to an APInt&, the compiler destroys the temporary the IntTy& was
referring to, leaving the APInt& referring to garbage.  This causes the unittest
to fail systematically on my machine; it can also be caught by running the test
under valgrind.

llvm-svn: 167356

0 (as nullptr) is incompatible to pointer in type matching on msvc.

llvm-svn: 167355

also do it for vectors of pointers.

llvm-svn: 167354

caret locations and source ranges in macros.  Makes ranges more accurate
in some cases, and fixes an assertion failure.

Fixes <rdar://problem/12472249>.

llvm-svn: 167353

This will simplify checkers that need to register for leaks. Currently,
they have to register for both: check dead and check end of path.

I've modified the SymbolReaper to consider everything on the stack dead
if the input StackLocationContext is 0.

(This is a bit disruptive, so I'd like to flash out all the issues
asap.)

llvm-svn: 167352

llvm-svn: 167351

Node builders should manage the nodes, not the context.

llvm-svn: 167350

Fix a little think-o.  In FileSpec::operator== we were trying to figure out whether the rhs file was resolved or not by comparing
the resolved version of the rhs FileSpec's directory name with the lhs FileSpec's directory name.  We really meant to compare it
with the rhs FileSpec's directory name...

<rdar://problem/12438838>

llvm-svn: 167349

instructions.

llvm-svn: 167348

llvm-svn: 167347

llvm-svn: 167346

llvm-svn: 167345

Be careful not to optimize a SELECT_CC into a SETCC post-legalization if the SETCC node would be illegal.

llvm-svn: 167344

Make sure users know that "target variable" can read variables while running a process by changing the documentation string.

llvm-svn: 167343

llvm-svn: 167342

register is needed.

llvm-svn: 167341

llvm-svn: 167340

llvm-svn: 167339

These are CallEvent-equivalents of helpers already accessible in
CheckerContext, as part of making it easier for new checkers to be written
using CallEvent rather than raw CallExprs.

llvm-svn: 167338

Also, Decls already carry a pointer to the ASTContext, so there's no need
to pass an extra argument to the predicate.

llvm-svn: 167337

llvm-svn: 167336

reserved. Without this fix, RegScavenger::getRegsAvailable incorrectly
returns an empty set of integer registers.

llvm-svn: 167335

llvm-svn: 167334

Add a stub for the x86 cost model impl. Implement a basic cost rule for inserting/extracting from XMM registers.

llvm-svn: 167333

llvm-svn: 167332

mrr mode.

llvm-svn: 167331

llvm-svn: 167330