summaryrefslogtreecommitdiffstats
path: root/lldb/source/Core/PluginManager.cpp
diff options
context:
space:
mode:
authorHal Finkel <hfinkel@anl.gov>2013-04-05 05:01:13 +0000
committerHal Finkel <hfinkel@anl.gov>2013-04-05 05:01:13 +0000
commite6f48e4e2f7a5f5c845d762a2651a24f759de32c (patch)
tree48bf2a4099ee074a103764890ab92f28b8a70788 /lldb/source/Core/PluginManager.cpp
parentfb6b9f48d04c8a25fdad43c13d092f253a72f371 (diff)
downloadbcm5719-llvm-e6f48e4e2f7a5f5c845d762a2651a24f759de32c.tar.gz
bcm5719-llvm-e6f48e4e2f7a5f5c845d762a2651a24f759de32c.zip
Fix bug in PEI's virtual-register scavenging
This change fixes a bug that I introduced in r178058. After a register is scavenged using one of the available spills slots the instruction defining the virtual register needs to be moved to after the spill code. The scavenger has already processed the defining instruction so that registers killed by that instruction are available for definition in that same instruction. Unfortunately, after this, the scavenger needs to iterate through the spill code and then visit, again, the instruction that defines the now-scavenged register. In order to avoid confusion, the register scavenger needs the ability to 'back up' through the spill code so that it can again process the instructions in the appropriate order. Prior to this fix, once the scavenger reached the just-moved instruction, it would assert if it killed any registers because, having already processed the instruction, it believed they were undefined. Unfortunately, I don't yet have a small test case. Thanks to Pranav Bhandarkar for diagnosing the problem and testing this fix. llvm-svn: 178845
Diffstat (limited to 'lldb/source/Core/PluginManager.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud