- Add a basic machine-level dead block eliminator.

These two have to go together, since many other parts of the code generator are unable to handle the unreachable blocks otherwise created.

llvm-svn: 54333

This allows it to work correctly on aggregate values.
This fixes PR2623.

llvm-svn: 54331

This allows it to work correctly on nested aggregate values.
This fixes PR2625.

llvm-svn: 54330

switches use the binary search algorithm) for
environments that don't support it.  PPC64 JIT
is such an environment; turn the flag on for that.

llvm-svn: 54248

llvm-svn: 54239

it isn't always visible to gdb.

llvm-svn: 54228

empty structs. This fixes PR2612.

llvm-svn: 54226

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

llvm-svn: 54225

llvm-svn: 54218

llvm-svn: 54186

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

llvm-svn: 54173

to be marked invalid regardless of whether it is
a debug, an exception handling or (hopefully) a
GC label.

llvm-svn: 54172

llvm-svn: 54168

The CellSPU codegen is broken, but needs to be fixed before we can
put this back in.

llvm-svn: 54164

CodeGen & Clang work coming next.

llvm-svn: 54161

a new ilist_node class, and remove them. Unlike alist_node,
ilist_node doesn't attempt to manage storage itself, so it avoids
the associated problems, including being opaque in gdb.

Adjust the Recycler class so that it doesn't depend on alist_node.
Also, change it to use explicit Size and Align parameters, allowing
it to work when the largest-sized node doesn't have the greatest
alignment requirement.

Change MachineInstr's MachineMemOperand list from a pool-backed
alist to a std::list for now.

llvm-svn: 54146

llvm-svn: 54136

the SelectionDAG's.

llvm-svn: 54129

llvm-svn: 54128

parallel its analogue, Value::value_use_iterator. The operator* method
now returns the user, rather than the use.

llvm-svn: 54127

llvm-svn: 54124

unary operations!  Add support for softening
some additional unary operations like fp_to_sint.

llvm-svn: 54122

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

llvm-svn: 54072

Special cases are needed in renumbering when dealing with renumbering after a PHI has been removed.  The interval previously defined
by the PHI needs to be extended to the beginning of its basic block, and the intervals that were inputs need to be trimmed to the end 
of their basic blocks.

llvm-svn: 54070

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

llvm-svn: 54065

llvm-svn: 54062

llvm-svn: 54061

This is tricky business, and will probably take a few more iterations to get
the last kinks out of it.

llvm-svn: 54043

regressions, such as PR2595. Also, there is a significant code-quality
issue in SPEC 464.h264ref and a few others.

llvm-svn: 54014

llvm-svn: 54007

dependencies with constant load nodes. This allows them to be scheduled
freely.

llvm-svn: 54001

and knowledge of PseudoSourceValues. This unfortunately isn't sufficient to allow
constants to be rematerialized in PIC mode -- the extra indirection is a
complication.

llvm-svn: 54000

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

llvm-svn: 53985

llvm-svn: 53961

to multiply the instruction count by a constant factor in a few places, which
caused the register allocator to require many more iterations.

llvm-svn: 53959

Remove the GetResultInst instruction. It is still accepted in LLVM assembly
and bitcode, where it is now auto-upgraded to ExtractValueInst. Also, remove
support for return instructions with multiple values. These are auto-upgraded
to use InsertValueInst instructions.

The IRBuilder still accepts multiple-value returns, and auto-upgrades them
to InsertValueInst instructions.

llvm-svn: 53941

llvm-svn: 53938