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: 54144

llvm-svn: 54142

of operands should be -1 not 0.

llvm-svn: 54141

Fixed COMM asm directive usage.
ConstantPool using custom FourByteConstantSection.

llvm-svn: 54139

llvm-svn: 54136

This fixes PR2599.

llvm-svn: 54133

circumstances we could end up remapping a dependee to the same instruction 
that we're trying to remove.  Handle this properly by just falling back to
a conservative solution.

llvm-svn: 54132

llvm-svn: 54131

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

mmx needs its own fancy shuffle logic based on unpack; for now we get correct but awful code.

Also commit Mon Ping's VSETCC patch

llvm-svn: 54039

llvm-svn: 54031

llvm-svn: 54030

llvm-svn: 54029

llvm-svn: 54028

llvm-svn: 54026

llvm-svn: 54025

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

llvm-svn: 54004

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

command-line option, and disable it by default. It introduced performance
regressions because CodeGen is currently not able to remat such loads.

llvm-svn: 53997

large numbers of CBE regressions caused by r53958.

llvm-svn: 53990

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

llvm-svn: 53985

Fix a catastrophic PPC64 ABI bug: i32 operands which are passed in memory (all of the parameter registers are used) are loaded from sp offsets that were off by 4.

llvm-svn: 53979

llvm-svn: 53973

Rename instance variables, parameter argument names to eliminate a bunch of compilation warnings with -Wshadow.

llvm-svn: 53970

llvm-svn: 53961