58 Commits

Author	SHA1	Message	Date
Jakob Stoklund Olesen	69bc9ac5f7	This method belonged in VirtRegMap. ... llvm-svn: 126002	2011-02-19 00:38:43 +00:00
Jakob Stoklund Olesen	0dd5f07ac0	Use VirtRegMap's Virt2SplitMap to keep track of the original live range before splitting. ... All new virtual registers created for spilling or splitting point back to their original. llvm-svn: 125980	2011-02-18 22:35:20 +00:00
Jakob Stoklund Olesen	e259b04730	Simplify the LiveRangeEdit::canRematerializeAt() interface a bit. ... llvm-svn: 118661	2010-11-10 01:05:12 +00:00
Jakob Stoklund Olesen	66012df062	Don't assign new registers created during a split to the same stack slot, but ... give them individual stack slots once the are actually spilled. llvm-svn: 117945	2010-11-01 19:49:57 +00:00
Jakob Stoklund Olesen	03fd8bf61c	Remember to keep track of rematted values. ... llvm-svn: 116962	2010-10-20 22:50:42 +00:00
Jakob Stoklund Olesen	9121d7b293	Move some of the InlineSpiller rematerialization code into LiveRangeEdit. ... llvm-svn: 116951	2010-10-20 22:00:51 +00:00
Jakob Stoklund Olesen	5d5bcb8ee4	Move stack slot assignments into LiveRangeEdit. ... All registers created during splitting or spilling are assigned to the same stack slot as the parent register. When splitting or rematting, we may not spill at all. In that case the stack slot is still assigned, but it will be dead. llvm-svn: 116546	2010-10-15 00:16:55 +00:00
Jakob Stoklund Olesen	acca65b973	Create a new LiveRangeEdit class to keep track of the new registers created when ... splitting or spillling, and to help with rematerialization. Use LiveRangeEdit in InlineSpiller and SplitKit. This will eventually make it possible to share remat code between InlineSpiller and SplitKit. llvm-svn: 116543	2010-10-14 23:49:52 +00:00