more than one successor. Normally, these extra successors are dead. However,
some of them may branch to exception handling landing pads. If we remove those
successors, then the landing pads could go away if all predecessors to it are
removed. Before, it was checking if the direct successor was the landing
pad. But it could be the result of jumping through multiple basic blocks to get
to it. If we were to only check for the existence of an EH_LABEL in the basic
block and not remove successors if it's in there, then it could stop actually
dead basic blocks from being removed.

llvm-svn: 91092

If VariableDIe is not created (may be because global was optimzed away) then do not try to use the variable die.

llvm-svn: 91077

It's not safe to coalesce a move where src and dst registers have different subregister indices. e.g.:
%reg16404:1<def> = MOV8rr %reg16412:2<kill>

llvm-svn: 91061

Create global variable DIEs after creating subprogram DIEs. This allows function level static variable's to find their context at the time of DIE creation.

llvm-svn: 91055

llvm-svn: 91051

The coalescer is supposed to clean these up, but when setting up parameters
for a function call, there may be copies to physregs. If the defining
instruction has been LICM'ed far away, the coalescer won't touch it.

The register allocation hint does not always work - when the register
allocator is backtracking, it clears the hints.

This patch is more conservative than r90502, and does not break
483.xalancbmk/i686. It still breaks the PowerPC bootstrap, so it is disabled
by default, and can be enabled with the -trivial-coalesce-ends option.

llvm-svn: 91049

llvm-svn: 90979

llvm-svn: 90970

When a call is placed to spill an interval this spiller will first try to
break the interval up into its component values. Single value intervals and
intervals which have already been split (or are the result of previous splits)
are spilled by the default spiller.

Splitting intervals as described above may improve the performance of generated
code in some circumstances. This work is experimental however, and it still
miscompiles many benchmarks. It's not recommended for general use yet.

llvm-svn: 90951

llvm-svn: 90925

Move isConsecutiveLoad to SelectionDAG. It's not target dependent and it's primary used by selectdag passes.

llvm-svn: 90922

llvm-svn: 90919

llvm-svn: 90918

llvm-svn: 90917

llvm-svn: 90898

There is no need to supply ModuleCU to addType() as a parameter.

llvm-svn: 90858

llvm-svn: 90857

llvm-svn: 90816

llvm-svn: 90815

llvm-svn: 90805

llvm-svn: 90804

llvm-svn: 90759

llvm-svn: 90744

Truncate the arguments of llvm.frameaddress / llvm.returnaddress intrinsics from i32 to platform's largest native type

llvm-svn: 90741

llvm-svn: 90669

llvm-svn: 90668

llvm-svn: 90653

And separate the directory and file name with a '/'.

llvm-svn: 90641

isn't cluttered with things like "Llabel47:Llabel48:  movq  (%rsi), %xmm3"

llvm-svn: 90638

llvm-svn: 90637

instead of SelectionDAGISel.cpp.

llvm-svn: 90636

MachineBasicBlock::canFallThrough(), which is target-independent and more
thorough.

llvm-svn: 90634

llvm-svn: 90633

and that Instruction only. Implement this by setting the "current debug position"
back to Unknown after processing each instruction.

llvm-svn: 90632

Don't print "SrcLine"; just print the filename and line number, which
is obvious enough and more informative.

llvm-svn: 90631

the column number if it is not known. Handle the case of a missing filename
better.

llvm-svn: 90630

llvm-svn: 90621

llvm-svn: 90617

Use new interfaces to print spill size.

llvm-svn: 90611

llvm-svn: 90575