To find the last use of a register unit, start from the bottom and scan
upwards until a user is found.

<rdar://problem/13353090>

llvm-svn: 176706

No test case, spotted by inspection.

llvm-svn: 176705

llvm-svn: 176703

llvm-svn: 176702

Fixes PR15344.

llvm-svn: 176701

fold selectcc (selectcc x, y, a, b, cc), b, a, b, setne ->
     selectcc x, y, a, b, cc

Reviewed-by: Christian König <christian.koenig@amd.com>
llvm-svn: 176700

Two changes:
1. Prefer SET* instructions when possible
2. Handle the CND*_INT case with floating-point args

Reviewed-by: Christian König <christian.koenig@amd.com>
llvm-svn: 176699

Reviewed-by: Christian König <christian.koenig@amd.com>
llvm-svn: 176698

Reviewed-by: Christian König <christian.koenig@amd.com>
llvm-svn: 176697

Reviewed-by: Christian König <christian.koenig@amd.com>
llvm-svn: 176696

llvm-svn: 176695

LegalizeDAG.cpp uses the value of the comparison operands when checking
the legality of BR_CC, so DAGCombiner should do the same.

v2:
  - Expand more BR_CC value types for NVPTX

v3:
  - Expand correct BR_CC value types for Hexagon, Mips, and XCore.

llvm-svn: 176694

AddressSpace definition has changed in a previous commit, reflect it
to avoid false failure.

llvm-svn: 176693

llvm-svn: 176692

Signed-off-by: Christian König <christian.koenig@amd.com>
llvm-svn: 176691

llvm-svn: 176689

Patch based on Mans Rullgard's.

llvm-svn: 176688

This is certainly not the last word on scheduling for this target, but
right now this allows a few apps to run / finish with radeonsi, most
notably UT2004 / Lightsmark. They fail to compile some shaders with the
default scheduler because it ends up trying to spill registers, which
we don't support yet (and which is probably a bad idea in general for
performance if it can be avoided).

NOTE: This is a candidate for the Mesa stable branch.

Reviewed-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Tom Stellard <thomas.stellard@amd.com>
llvm-svn: 176687

This verifies live intervals both before and after scheduling. It's
useful for anyone hacking on live interval update.

Note that we don't yet pass verification all the time. We don't yet
handle updating nonallocatable live intervals perfectly.

llvm-svn: 176685

llvm-svn: 176679

Not sure why these aren't failing on my linux machine, but this should cover
it.

llvm-svn: 176678

Code generation makes some basic assumptions about the IR it's been given. In
particular, if there is only one 'invoke' in the function, then that invoke
won't be going away. However, with the advent of the `llvm.donothing' intrinsic,
those invokes may go away. If all of them go away, the landing pad no longer has
any users. This confuses the back-end, which asserts.

This happens with SjLj exceptions, because that's the model that modifies the IR
based on there being invokes, etc. in the function.

Remove any invokes of `llvm.donothing' during SjLj EH preparation. This will
give us a CFG that the back-end won't be confused about. If all of the invokes
in a function are removed, then the SjLj EH prepare pass won't insert the bogus
code the relies upon the invokes being there.
<rdar://problem/13228754&13316637>

llvm-svn: 176677

GCC was the system compiler on the mac.

llvm-svn: 176675

Mostly this is just changing the named metadata (llvm.dbg.sp, llvm.dbg.gv,
llvm.dbg.<func>.lv, etc -> llvm.dbg.cu), adding a few fields to older records
(DIVariable: flags/inlined-at, DICompileUnit: sp/gv/types,
DISubprogram: local variables list)

The tests to update were discovered by a change I'm working on to remove debug
info version support - so any tests using old debug info versions I haven't
updated probably are bad tests or just not actually designed to test debug
info.

llvm-svn: 176671

llvm-svn: 176669

In very rare cases caused by irreducible control flow, the dominating
block can have the same trace head without actually being part of the
trace.

As long as such a dominator still has valid instruction depths, it is OK
to use it for computing instruction depths.

Rename the function to avoid lying, and add a check that instruction
depths are computed for the dominator.

llvm-svn: 176668

llvm-svn: 176661

llvm-svn: 176660

rdar://13370942

llvm-svn: 176659

llvm-svn: 176652

llvm-svn: 176651

rdar://13370942

llvm-svn: 176649

llvm-svn: 176648

llvm-svn: 176647

llvm-svn: 176646

llvm-svn: 176645

llvm-svn: 176643

llvm-svn: 176642

coding in the other places of the file.

llvm-svn: 176641

llvm-svn: 176638