aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Writer/BitcodeWriterPass.cpp
diff options
context:
space:
mode:
authorEvan Cheng <evan.cheng@apple.com>2007-11-17 00:40:40 +0000
committerEvan Cheng <evan.cheng@apple.com>2007-11-17 00:40:40 +0000
commit8e22379303930b9396c7bee1d5c569c40a012e9e (patch)
treed00716ba868ca03be235e7f59b55ab833df3e59b /llvm/lib/Bitcode/Writer/BitcodeWriterPass.cpp
parentaa72f72bd3ab7fe2eed1d2407800d696d0a18f36 (diff)
downloadllvm-8e22379303930b9396c7bee1d5c569c40a012e9e.zip
llvm-8e22379303930b9396c7bee1d5c569c40a012e9e.tar.gz
llvm-8e22379303930b9396c7bee1d5c569c40a012e9e.tar.bz2
Live interval splitting:
When a live interval is being spilled, rather than creating short, non-spillable intervals for every def / use, split the interval at BB boundaries. That is, for every BB where the live interval is defined or used, create a new interval that covers all the defs and uses in the BB. This is designed to eliminate one common problem: multiple reloads of the same value in a single basic block. Note, it does *not* decrease the number of spills since no copies are inserted so the split intervals are *connected* through spill and reloads (or rematerialization). The newly created intervals can be spilled again, in that case, since it does not span multiple basic blocks, it's spilled in the usual manner. However, it can reuse the same stack slot as the previously split interval. This is currently controlled by -split-intervals-at-bb. llvm-svn: 44198
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriterPass.cpp')
0 files changed, 0 insertions, 0 deletions