diff options
author | Nikita Popov <npopov@redhat.com> | 2025-06-23 12:44:14 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2025-06-23 12:44:14 +0200 |
commit | cfcb7888c71c7b5468e3fc55b6de0804403dc3fe (patch) | |
tree | 5faac64c09da4ce35724652bf2f71d2121e69a54 /lldb/packages/Python/lldbsuite/test | |
parent | e56384ff540e68f9d0500fa27a95354c0730e37b (diff) | |
download | llvm-cfcb7888c71c7b5468e3fc55b6de0804403dc3fe.zip llvm-cfcb7888c71c7b5468e3fc55b6de0804403dc3fe.tar.gz llvm-cfcb7888c71c7b5468e3fc55b6de0804403dc3fe.tar.bz2 |
[EarlyCSE] Fix dead store elimination for unwinding readnone calls (#145287)
EarlyCSE already resets LastStore when it hits an potentially unwinding
instruction, as the memory state may be observed by the caller after the
unwind.
There also was a test specifically making sure that this works even for
unwinding readnone calls -- however, the call in that test did not
participate in EarlyCSE in the first place, because it returns void
(relaxing that is how I got here), so it was not actually testing the
right thing.
Move the check for unwinding instructions earlier, so it also handles
the readnone case.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test')
0 files changed, 0 insertions, 0 deletions