isReg, etc., from isRegister, etc.

llvm-svn: 57006

Use a multimap rather than a map for holding the list of copies to insert, so we don't lose copies when two of them have
the same source.  I don't know what I was thinking when I wrote this originally.
Note: There's probably a more efficient way to do this, but I need to think about it some more, and about what determinism
guarantees need to be present.

llvm-svn: 56964

llvm-svn: 56893

llvm-svn: 56674

llvm-svn: 56567

llvm-svn: 56485

just use LI::MergeValueAsValue, as its behavior in the presence of overlapping ranges
isn't what StrongPHIElimination wants.

llvm-svn: 56472

llvm-svn: 55779

llvm-svn: 54780

llvm-svn: 54742

2) Conditionalize temporary insertion if we don't need it.

llvm-svn: 54741

Do a dominator walk when scheduling copies, rather than a DFS on the CFG.  Also, fix a few problems when creating
live intervals for temporaries created by phi elimination.

llvm-svn: 54483

Correct handle cases where two phis are coalesced together, and correct break up the case where two different
phis want to coalesce with the same vreg.

llvm-svn: 54426

llvm-svn: 54422

llvm-svn: 54421

llvm-svn: 54371

llvm-svn: 54369

Use existing LiveInterval methods to simplify live interval merging.  Thanks to Evan for pointing these out.

llvm-svn: 54225

When merging live intervals, we also need to merge in any live ranges that are inputs to two-address instructions
that themselves define a range we already care about.

llvm-svn: 54185

When merging a PHI operand's live interval into the PHI's live interval, we need to merge over all liveranges in
the operand's interval that share the relevant value number, not just the range that immediately precedes the PHI.

llvm-svn: 54174

Fix the issues originally addressed in r54070.  After thinking about it some more, I realized that the right thing to do
is to have StrongPHIElimination use its knowledge of the PHIs before they're erased to update the intervals appropriate.  This is
both simpler and more accurate than the alternative, which was having LIA figure it out when it renumbered things, plus it's just
the right thing to do!

llvm-svn: 54077

to the handled set so it will get filtered out in future iterations.

llvm-svn: 54065

llvm-svn: 54062

Store the predecessor MBB in the PHIUnion, rather than an index, since the indices will change after renumbering.

llvm-svn: 53985

llvm-svn: 52016

llvm-svn: 52013

Correctly construct live intervals for the copies we inserted into the predecessors of a block containing a PHI.

llvm-svn: 51950

llvm-svn: 51922

Preserve the register coallescer, and update live intervals more correctly by triggering a renumbering after phi elimination.

llvm-svn: 51780

address of the PassInfo directly instead of calling getPassInfo.
This eliminates a bunch of dynamic initializations of static data.

Also, fold RegisterPassBase into PassInfo, make a bunch of its
data members const, and rearrange some code to initialize data
members in constructors instead of using setter member functions.

llvm-svn: 51022

several things that were neither in an anonymous namespace nor static
but not intended to be global.

llvm-svn: 51017

node and its inputs.

llvm-svn: 49070

unknown defining inst after PHI elimination.

llvm-svn: 49069

llvm-svn: 49043

llvm-svn: 48973

Remove some unneeded code for LiveInterval joining, and fix a bug in the Phi elimination algorithm where we were accidentally reasoning about
the source rather than the destination.

llvm-svn: 48936

llvm-svn: 48811

llvm-svn: 48803

llvm-svn: 48802

llvm-svn: 48739