Matt Arsenault f1cce1cf54 Add an ID field to StackObjects ... On AMDGPU SGPR spills are really spilled to another register. The spiller creates the spills to new frame index objects, which is used as a placeholder. This will eventually be replaced with a reference to a position in a VGPR to write to and the frame index deleted. It is most likely not a real stack location that can be shared with another stack object. This is a problem when StackSlotColoring decides it should combine a frame index used for a normal VGPR spill with a real stack location and a frame index used for an SGPR. Add an ID field so that StackSlotColoring has a way of knowing the different frame index types are incompatible. llvm-svn: 308673		2017-07-20 21:03:45 +00:00
..
atomic-memoperands.mir
cfi-def-cfa.mir
expected-target-flag-name.mir
generic-virtual-registers-error.mir
generic-virtual-registers-with-regbank-error.mir
intrinsics.mir
invalid-target-flag-name.mir
invalid-target-memoperands.mir	[MIR] Add support for printing and parsing target MMO flags	2017-07-13 02:28:54 +00:00
lit.local.cfg
multiple-lhs-operands.mir
register-operand-bank.mir
spill-fold.mir
stack-object-local-offset.mir	Add an ID field to StackObjects	2017-07-20 21:03:45 +00:00
target-flags.mir
target-memoperands.mir	[AArch64][Falkor] Avoid HW prefetcher tag collisions (step 1)	2017-07-14 21:44:12 +00:00