llvm-svn: 132479

llvm-svn: 132477

Testcase will come when we use it.

Part of rdar://9119939

llvm-svn: 132476

Create new class, InputReaderStack, to better handle 
mutexes around input readers and prevent deadlocking; modify
Debugger to use the new class.

llvm-svn: 132475

llvm-svn: 132474

llvm-svn: 132472

This saves two virtual function calls and an Allocatable BitVector test,
making RAFast run 2% faster.

llvm-svn: 132471

llvm-svn: 132470

llvm-svn: 132468

Parsing a register name/number for .cfi directives can't assume that a
register name starts with a '%' token. Be more flexible and check for a
register number instead. Still unlikely to be perfect, but it allows us
to parse both plain identifiers as register names and integers as register
numbers, which is what we're wanting to support at this point.

llvm-svn: 132466

llvm-svn: 132462

llvm-svn: 132461

llvm-svn: 132460

llvm-svn: 132459

rdar://problem/6373334

llvm-svn: 132458

Found by valgrind.

llvm-svn: 132457

llvm-svn: 132456

No functional change.

llvm-svn: 132455

llvm-svn: 132454

+keyPathsForValuesAffecting<Key> completion was mislabeled as an
instance method, and +automaticallyNotifiesObserversOf<Key> was
missing entirely. Fixes <rdar://problem/9516762>.

llvm-svn: 132452

llvm-svn: 132451

register classes.

It provides information for each register class that cannot be
determined statically, like:

- The number of allocatable registers in a class after filtering out the
  reserved and invalid registers.

- The preferred allocation order with registers that overlap callee-saved
  registers last.

- The last callee-saved register that overlaps a given physical register.

This information usually doesn't change between functions, so it is
reused for compiling multiple functions when possible.  The many
possible combinations of reserved and callee saves registers makes it
unfeasible to compute this information statically in TableGen.

Use RegisterClassInfo to count available registers in various heuristics
in SimpleRegisterCoalescing, making the pass run 4% faster.

llvm-svn: 132450

llvm-svn: 132449

llvm-svn: 132448

llvm-svn: 132447

Revert r132426; this test passes more often than not, and we don't have a way to mark tests as intermittently failing at the moment.

llvm-svn: 132446

llvm-svn: 132445

llvm-svn: 132444

llvm-svn: 132443

When marking a block as being unanalyzable, use "Clobber" on the terminator instead of the first instruction in the block.  This is a bit of a hack; "Clobber" isn't really the right marking in the first place.  memdep doesn't really have any way of properly expressing "unanalyzable" at the moment.  Using it on the terminator is much less ambiguous than using it on an arbitrary instruction, though.

In the given testcase, the "Clobber" was pointing to a load, and GVN was incorrectly assuming that meant that the "Clobber" load overlapped the load being analyzed (when they are actually unrelated).

The included testcase tests both this commit and r132434.

Part two of rdar://9429882.  (r132434 was mislabeled.)

llvm-svn: 132442

Turn off printing of command sent to the pexpect-spawned child process to make the script more robotic.

llvm-svn: 132441

llvm-svn: 132440

llvm-svn: 132439

This serves as a regression test against rdar://problem/9530511.

llvm-svn: 132438

llvm-svn: 132437

rdar://problem/9530511

llvm-svn: 132435

In MemoryDependenceAnalysis::getNonLocalPointerDepFromBB, if a given block is is deemed unanalyzable (and we execute one of the "goto PredTranslationFailure" statements), make sure we don't put information about the predecessors of that block into the returned data structures; this can lead to, among other things, extraneous results (which will confuse passes using memdep).  Fixes an assert in GVN compiling ruby. Part of rdar://problem/9521954 .

Testcase coming up soon.

llvm-svn: 132434

llvm-svn: 132433

llvm-svn: 132432

nested types, from Michael Han!

llvm-svn: 132431