diff options
| author | George Burgess IV <george.burgess.iv@gmail.com> | 2018-08-22 22:34:38 +0000 |
|---|---|---|
| committer | George Burgess IV <george.burgess.iv@gmail.com> | 2018-08-22 22:34:38 +0000 |
| commit | 5676a5d48cb8764341d7b6da0251b7988078be24 (patch) | |
| tree | d705b0bbc363e908f17f70d8493c24897b10b8d0 /lldb/packages/Python/lldbsuite/test/python_api/default-constructor | |
| parent | a8accca4f598576cab06bd1917bbba59ec1513b9 (diff) | |
| download | bcm5719-llvm-5676a5d48cb8764341d7b6da0251b7988078be24.tar.gz bcm5719-llvm-5676a5d48cb8764341d7b6da0251b7988078be24.zip | |
[MemorySSA] Invalidate optimized Defs upon moving them; NFC
We're currently getting this behavior implicitly, since we determine if
a Def's optimization is valid based on the ID of its defining access.
This is incorrect, though I wouldn't be surprised if this was masked in
part by that we're using a WeakVH to track what Defs are optimized to.
(Not to mention that we don't move Defs super often, AFAICT). I'll
submit a patch to fix this shortly.
This also includes a minor refactor to reduce duplication a bit.
No test is included, since like said, this already happens to be our
behavior. I'll add a test for this with my fix to the other bug
mentioned above.
llvm-svn: 340461
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/default-constructor')
0 files changed, 0 insertions, 0 deletions
