1. http://gcc.gnu.org/wiki/TemplateParmsDwarf
2. ftp://ftp.software.ibm.com/software/os390/czos/dwarf/mips_extensions.pdf

llvm-svn: 139784

There is only one legitimate use remaining, in addIntervalsForSpills().
All other calls to hasPHIKill() are only used to update PHIKill flags.

The addIntervalsForSpills() function is part of the old spilling
framework, only used by linearscan.

llvm-svn: 139783

Instead, let HasOtherReachingDefs() test for defs in B that overlap any
phi-defs in A as well.  This test is slightly different, but almost
identical.

A perfectly precise test would only check those phi-defs in A that are
reachable from AValNo.

llvm-svn: 139782

The source live range is recomputed using shrinkToUses() which does
handle phis correctly.  The hasPHIKill() condition was relevant in the
old days when ReMaterializeTrivialDef() tried to recompute the live
range itself.

The shrinkToUses() function will mark the original def as dead when no
more uses and phi kills remain.  It is then removed by
runOnMachineFunction().

llvm-svn: 139781

It is conservatively correct to keep the hasPHIKill flags, even after
deleting PHI-defs.

The calculation can be very expensive after taildup has created a
quadratic number of indirectbr edges in the CFG, and the hasPHIKill flag
isn't used for anything after RenumberValues().

llvm-svn: 139780

Note that DW_TAG_rvalue_reference_type is officially 0x42, not 0x41.

llvm-svn: 139779

Thanks Nick!

llvm-svn: 139778

llvm-svn: 139777

llvm-svn: 139776

llvm-svn: 139775

llvm-svn: 139774

llvm-svn: 139773

The llvm-dwarfdump output isn't very verbose yet.

llvm-svn: 139771

llvm-svn: 139768

An improper SlotIndex->VNInfo lookup was leading to unsafe copy removal.
Fixes PR10920 401.bzip2 miscompile with no IV rewrite.

llvm-svn: 139765

Fix the code creating VZEXT_LOAD so that it creates the right memoperand.  Issue spotted in -debug output.  I can't think of any practical effects at the moment, but it might matter if we start doing more aggressive alias analysis in CodeGen.

llvm-svn: 139758

will ignore the erasedOnReboot option, and properly escape the
backslash in "C:\TEMP". Thanks to Aaron and Francois.

llvm-svn: 139755

llvm-svn: 139754

llvm-svn: 139753

llvm-svn: 139751

llvm-svn: 139748

llvm-svn: 139747

Patch by Joakim Johansson!

llvm-svn: 139743

llvm-svn: 139739

llvm-svn: 139736

llvm-svn: 139735

Ported from LLDB.

llvm-svn: 139732

temporary data. 

llvm-svn: 139725

Fix a bug in handling default flags for both ARM and Thumb encodings.

llvm-svn: 139721

Select the right 16 vs. 32 bit encoding in an IT block.

llvm-svn: 139714

llvm-svn: 139712

which could theoretically throw.

llvm-svn: 139710

in memory relevant to the optimizer. rdar://10050579.

llvm-svn: 139708

Clean up register list handling in general a bit to explicitly check things
like all the registers being from the same register class.

rdar://8883573

llvm-svn: 139707

llvm-svn: 139705

THe LRE_DidCloneVirtReg callback may be called with vitual registers
that RAGreedy doesn't even know about yet.  In that case, there are no
data structures to update.

llvm-svn: 139702

llvm-dwarfdump: Make the "is debug info section" heuristic stricter so it doesn't accidentaly picks up the wrong section.

Also add some validation code to the aranges section parser.

Fixes PR10926.

llvm-svn: 139701

llvm-svn: 139699

When a back-copy is hoisted to the nearest common dominator, keep
looking up the dominator tree for a less loopy dominator, and place the
back-copy there instead.

Don't do this when a single existing back-copy dominates all the others.
Assume the client knows what he is doing, and keep the dominating
back-copy.

This prevents us from hoisting back-copies into loops in most cases.  If
a value is defined in a loop with multiple exits, we may still hoist
back-copies into that loop.  That is the speed/size tradeoff.

llvm-svn: 139698

llvm-svn: 139697