diff options
author | George Burgess IV <george.burgess.iv@gmail.com> | 2019-03-21 03:11:34 +0000 |
---|---|---|
committer | George Burgess IV <george.burgess.iv@gmail.com> | 2019-03-21 03:11:34 +0000 |
commit | ae84e9ab49087a460e74831029d98cb519271a9a (patch) | |
tree | 370fca2fd3bf5b290c18e9b2d1f018416df4687b /lldb/source/Plugins/Process/gdb-remote | |
parent | c9f4cbf7a62ae720accc962942dbdb58747d92e5 (diff) | |
download | bcm5719-llvm-ae84e9ab49087a460e74831029d98cb519271a9a.tar.gz bcm5719-llvm-ae84e9ab49087a460e74831029d98cb519271a9a.zip |
[MSSA] Delete move ctor; remove dynamic never-moved verification
Code archaeology in D59315 revealed that MSSA should never be moved.
Rather than trying to check dynamically that this hasn't happened in the
verify() functions of Walkers, it's likely best to just delete its move
constructor.
Since all these verify() functions did is check that MSSA hasn't moved,
this allows us to remove these verify functions.
I can readd the verification checks if someone's super concerned about
us trying to `memcpy` MemorySSA or something somewhere, but I imagine we
have other problems if we're trying anything like that...
llvm-svn: 356641
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote')
0 files changed, 0 insertions, 0 deletions