llvm-svn: 138487

llvm-svn: 138486

llvm-svn: 138481

[analyzer] MacOSKeychainAPIChecker: Provide reacher diagnostic trace by pointing to the allocation site when reporting a leak.

llvm-svn: 138479

llvm-svn: 138478

llvm-svn: 138477

[analyzer] Copy GC mode setting from CFRefCount to RetainReleaseChecker in preparation for getting rid of CFRefCount.

This is a little hacky for now but will get better once we decide the best way to handle this.

llvm-svn: 138476

llvm-svn: 138475

[analyzer] Allow checker writes to specify that no region should be accosiated with the report. (Useful when we report an error on endOfPath or deadSymbols, when the range of the last expression might have nothing to do with the error.)

llvm-svn: 138474

insertion place.

llvm-svn: 138473

llvm-svn: 138472

llvm-svn: 138470

llvm-svn: 138469

rdar://10015134

llvm-svn: 138467

llvm-svn: 138466

llvm-svn: 138465

This is a very small regression (actually introduced in r138309) because it won't catch leaks of objects passed by reference to CFDictionaryCreate (they're considered to have escaped and are ignored). If this is important we can put in a specific eval::Call to restore the functionality.

llvm-svn: 138464

module DAG-based lookup scheme. This required some reshuffling, so
that each module stores its own mapping from DeclContexts to their
lexical and visible sets for those DeclContexts (rather than one big
"chain"). 

Overall, this allows simple qualified name lookup into the translation
unit to gather results from multiple modules, with the lookup results
in module B shadowing the lookup results in module A when B imports A.

Walking all of the lexical declarations in a module DAG is still a
mess; we'll end up walking the loaded module list backwards, which
works fine for chained PCH but doesn't make sense in a DAG. I'll
tackle this issue as a separate commit.

llvm-svn: 138463

[analyzer] Slightly clean up the fix in 138432, so that it doesn't depend on the relative ordering of path-sensitive and path-insensitive checks. Still not ideal, but I think a real fix would require infrastructure that doesn't exist yet.

llvm-svn: 138462

llvm-svn: 138461

Thread safety: Fix a few typos in last commit -- use LockID instead of Lock in comments and start a couple methods with a lowercase letter

llvm-svn: 138460

llvm-svn: 138458

rdar://10014745

llvm-svn: 138457

llvm-svn: 138454

llvm-svn: 138452

llvm-svn: 138451

These are strictly utilities for registering targets and components.

llvm-svn: 138450

dominator information even though dominators were previously computed.

Patch by Nick Sumner.

llvm-svn: 138449

llvm-svn: 138448

Moved the test code for Python commands out of the test case for aliases, into its own dedicated test case (one fill was still lurking in the old folder)

llvm-svn: 138446

Add the predicate operand to the instructions. Update the back end
accordingly where the instructions are used. Restrict the SP operands
to actually only be SP, as otherwise these break assembly parsing for the
normal instruction variants.

llvm-svn: 138445

Moved the test code for Python commands out of the test case for aliases, into its own dedicated test case

llvm-svn: 138444

Be stricter in enforcing IT instruction predicate values, so that we don't end up trying to print out an illegal predicate.

llvm-svn: 138443

llvm-svn: 138442

llvm-svn: 138441

llvm-svn: 138437

Reset FirstID (first diagnostic's file ID) to allow for invocations of the VerifyDiagnosticsClient on several input files.

llvm-svn: 138434

variable sized alloca.

llvm-svn: 138433

[analyzer] Fix a Heisenbug concerning object lifetimes with a hack. Hopefully a better fix coming soon. See comment for more details.

llvm-svn: 138432

[analyzer] Reapply 138390 "Clean up unused bits of CFRefCount", reverted in 138405. Ended up unrelated to any problems.

llvm-svn: 138431