try to put a kill flag on a DBG_INFO instruction.

llvm-svn: 102820

Seen in SingleSrc/Benchmarks/Misc/flops with TEST=optllcdbg.
7929951.

llvm-svn: 102819

llvm-svn: 102817

modified.

llvm-svn: 102816

sub-register indices and outputs a single super register which is formed from
a consecutive sequence of registers.

This is used as register allocation / coalescing aid and it is useful to
represent instructions that output register pairs / quads. For example,
v1024, v1025 = vload <address>
where v1024 and v1025 forms a register pair.

This really should be modelled as
v1024<3>, v1025<4> = vload <address>
but it would violate SSA property before register allocation is done.

Currently we use insert_subreg to form the super register:
v1026 = implicit_def
v1027 - insert_subreg v1026, v1024, 3
v1028 = insert_subreg v1027, v1025, 4
...
      = use v1024
      = use v1028

But this adds pseudo live interval overlap between v1024 and v1025.

We can now modeled it as
v1024, v1025 = vload <address>
v1026 = REG_SEQUENCE v1024, 3, v1025, 4
...
      = use v1024
      = use v1026

After coalescing, it will be
v1026<3>, v1025<4> = vload <address>
...
      = use v1026<3>
      = use v1026

llvm-svn: 102815

code, and to eliminate the need for the SelectionDAGBuilder
state to be live during CodeGenAndEmitDAG calls.

Call SDB->clear() before CodeGenAndEmitDAG calls instead of
before it, and move the CurDAG->clear() out of SelectionDAGBuilder,
which doesn't own the DAG, and into CodeGenAndEmitDAG.

llvm-svn: 102814

llvm-svn: 102812

llvm-svn: 102810

changes before doing phi lowering for switches.

llvm-svn: 102809

llvm-svn: 102803

llvm-svn: 102802

llvm-svn: 102800

llvm-svn: 102799

were still inlining self-recursive functions into other functions.

Inlining a recursive function into itself has the potential to
reduce recursion depth by a factor of 2, inlining a recursive
function into something else reduces recursion depth by exactly 
1.  Since inlining a recursive function into something else is a
weird form of loop peeling, turn this off.

The deleted testcase was added by Dale in r62107, since then
we're leaning towards not inlining recursive stuff ever.  In any
case, if we like inlining recursive stuff, it should be done 
within the recursive function itself to get the algorithm 
recursion depth win.

llvm-svn: 102798

indexes could be of a different value type. Or not even using the same SDNode
for the constant (weird, I know). Compare the actual values instead of the
pointers.

llvm-svn: 102791

llvm-svn: 102781

instruction selection is done; it's confusing to see parts of it printed,
while other parts are omitted, along the way.

llvm-svn: 102771

call that might throw. The landing pad assumes that all registers are in stack
slots.

We used to spill those dirty CSRs after the call, and the stack slots would be
wrong when arriving at the landing pad.

llvm-svn: 102770

and fix a bug in BitVector's reference proxy class which this exposed.

llvm-svn: 102768

(and wrong).

llvm-svn: 102763

Radar 7927803

llvm-svn: 102760

on the original variables, so it's easier to see what is being done
to which blocks.

llvm-svn: 102759

llvm-svn: 102752

llvm-svn: 102751

llvm-svn: 102746

llvm-svn: 102743

llvm-svn: 102742

llvm-svn: 102741

llvm-svn: 102740

for unsigned purposes, so >64-bit integer values get a full all-ones
value.

llvm-svn: 102739

llvm-svn: 102734

llvm-svn: 102733

llvm-svn: 102731

llvm-svn: 102730

Rounding differences causes tests to fail on Linux.

llvm-svn: 102729

llvm-svn: 102728

llvm-svn: 102722

comparisons sign-extended to a different bitwidth than the
comparison operands.

llvm-svn: 102721

llvm-svn: 102720

folks. LLVM/Clang is miscompiled by the standard GCC at -O3.

llvm-svn: 102719