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

live intervals itself to use an instruction count approximation that is 
not affected by inserting empty indices.

llvm-svn: 53937

Fix pr2566: incorrect assumption about bit_convert. It doesn't not have to output a vector value. Patch by Nicolas Capens!

llvm-svn: 53932

and use the right result number, in the off chance that the graph root
has multiple result values.

llvm-svn: 53923

llvm-svn: 53896

llvm-svn: 53889

llvm-svn: 53884

SelectionDAG graph writer to make use of them. Now, nodes with multiple
values are displayed as such, with incoming edges pointing to the
specific value they use.

llvm-svn: 53875

llvm-svn: 53874

that include useful information like the name of the
block being viewed and the current phase of compilation.

llvm-svn: 53872

llvm-svn: 53870

in the MachineInstr clone code.

llvm-svn: 53868

generic SDNode's (nodes with their own constructors
should do sanity checking in the constructor).  Add
sanity checks for BUILD_VECTOR and fix all the places
that were producing bogus BUILD_VECTORs, as found by
"make check".  My favorite is the BUILD_VECTOR with
only two operands that was being used to build a
vector with four elements!

llvm-svn: 53850

If .loc and .file aren't used, always emit the "debug_line" section. This
requires at least one entry in the line matrix. So if there's nothing to emit
into the matrix, emit an end of matrix value anyway.

llvm-svn: 53803

llvm-svn: 53779

Richard Pennington.

llvm-svn: 53773

llvm-svn: 53772

the night realising that it was wrong :)  I
think the reason the same type was being used
for the shufflevec of indices as for the actual
indices is so that if one of them needs splitting
then so does the other.  After my patch it might
be that the indices need splitting but not the
rest, yet there is no good way of handling that.
I think the right solution is to not have the
shufflevec be an operand at all: just have it
be the list of numbers it actually is, stored
as extra info in the node.

llvm-svn: 53768

llvm-svn: 53766