Commits · fa222dfbed6631341f4b0b725ee4bc78d5fed33d · Roger Ferrer / llvm-epi-0.8

Nov 10, 2010
- Simplify the LiveRangeEdit::canRematerializeAt() interface a bit. · de5c4dc2
  Jakob Stoklund Olesen authored Nov 10, 2010
```
llvm-svn: 118661
```
  de5c4dc2
Nov 01, 2010
- Don't assign new registers created during a split to the same stack slot, but · ba9a4985
  Jakob Stoklund Olesen authored Nov 01, 2010
```
give them individual stack slots once the are actually spilled.

llvm-svn: 117945
```
  ba9a4985
Oct 21, 2010
- Remember to keep track of rematted values. · a3b61d32
  Jakob Stoklund Olesen authored Oct 20, 2010
```
llvm-svn: 116962
```
  a3b61d32
- Move some of the InlineSpiller rematerialization code into LiveRangeEdit. · 2edaa2fb
  Jakob Stoklund Olesen authored Oct 20, 2010
```
llvm-svn: 116951
```
  2edaa2fb
Oct 15, 2010

Move stack slot assignments into LiveRangeEdit. · 0f3e98ce

Jakob Stoklund Olesen authored Oct 15, 2010

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

0f3e98ce

Create a new LiveRangeEdit class to keep track of the new registers created when · 72911e49

Jakob Stoklund Olesen authored Oct 14, 2010

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

72911e49