diff options
author | Jakob Stoklund Olesen <stoklund@2pi.dk> | 2011-08-02 21:53:03 +0000 |
---|---|---|
committer | Jakob Stoklund Olesen <stoklund@2pi.dk> | 2011-08-02 21:53:03 +0000 |
commit | 0e0a8806d49038b60a0c20427d9f410b01cbb012 (patch) | |
tree | 9a33b338d2ead7da2d2043b367fe301fe05b275a /lib/Transforms/InstCombine/InstructionCombining.cpp | |
parent | f78faf84a85262bf76295dfc5d85e1e7a942a4f2 (diff) | |
download | external_llvm-0e0a8806d49038b60a0c20427d9f410b01cbb012.zip external_llvm-0e0a8806d49038b60a0c20427d9f410b01cbb012.tar.gz external_llvm-0e0a8806d49038b60a0c20427d9f410b01cbb012.tar.bz2 |
Extend the SpillPlacement interface with two new features.
The PrefBoth constraint is used for blocks that ideally want a live-in
value both on the stack and in a register. This would be used by a block
that has a use before interference forces a spill.
Secondly, add the ChangesValue flag to BlockConstraint. This tells
SpillPlacement if a live-in value on the stack can be reused as a
live-out stack value for free. If the block redefines the virtual
register, a spill would be required for that.
This extra information will be used by SpillPlacement to more accurately
calculate spill costs when a value can exist both on the stack and in a
register.
The simplest example is a basic block that reads the virtual register,
but doesn't change its value. Spilling around such a block requires a
reload, but no spill in the block.
The spiller already knows this, but the spill placer doesn't. That can
sometimes lead to suboptimal regions.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@136731 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'lib/Transforms/InstCombine/InstructionCombining.cpp')
0 files changed, 0 insertions, 0 deletions