History log of /llvm-project/llvm/lib/CodeGen/LiveRangeEdit.cpp (Results 151 – 156 of 156)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
# de5c4dc2 10-Nov-2010 Jakob Stoklund Olesen <stoklund@2pi.dk>

Simplify the LiveRangeEdit::canRematerializeAt() interface a bit.

llvm-svn: 118661


# ba9a4985 01-Nov-2010 Jakob Stoklund Olesen <stoklund@2pi.dk>

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


# a3b61d32 20-Oct-2010 Jakob Stoklund Olesen <stoklund@2pi.dk>

Remember to keep track of rematted values.

llvm-svn: 116962


# 2edaa2fb 20-Oct-2010 Jakob Stoklund Olesen <stoklund@2pi.dk>

Move some of the InlineSpiller rematerialization code into LiveRangeEdit.

llvm-svn: 116951


# 0f3e98ce 15-Oct-2010 Jakob Stoklund Olesen <stoklund@2pi.dk>

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 no

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

show more ...


# 72911e49 14-Oct-2010 Jakob Stoklund Olesen <stoklund@2pi.dk>

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 wil

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

show more ...


1234567