summaryrefslogtreecommitdiffstats
path: root/llvm/lib/CodeGen/MachineBasicBlock.cpp
diff options
context:
space:
mode:
authorChris Lattner <sabre@nondot.org>2006-05-01 22:03:24 +0000
committerChris Lattner <sabre@nondot.org>2006-05-01 22:03:24 +0000
commitfd0a5478a19823e836207b4b7900f567bc608dbd (patch)
tree0fe573436056189a65429a3c789d345eac2b7aeb /llvm/lib/CodeGen/MachineBasicBlock.cpp
parentab7dbe0cc9f06f4c0ab049d5421047c1a81879d5 (diff)
downloadbcm5719-llvm-fd0a5478a19823e836207b4b7900f567bc608dbd.tar.gz
bcm5719-llvm-fd0a5478a19823e836207b4b7900f567bc608dbd.zip
Fix a latent bug that my spiller patch last week exposed: we were leaving
instructions in the virtregfolded map that were deleted. Because they were deleted, newly allocated instructions could end up at the same address, magically finding themselves in the map. The solution is to remove entries from the map when we delete the instructions. llvm-svn: 28041
Diffstat (limited to 'llvm/lib/CodeGen/MachineBasicBlock.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud