diff options
| author | Ta-Wei Tu <tu.da.wei@gmail.com> | 2021-03-09 13:31:20 +0800 |
|---|---|---|
| committer | Ta-Wei Tu <tu.da.wei@gmail.com> | 2021-03-09 13:32:34 +0800 |
| commit | cf82700af8c658ae09b14c3d01bb1e73e48d3bd3 (patch) | |
| tree | dc72048bcc021c3099320585bff6013d0de3648c /lldb/source/Plugins/ScriptInterpreter/Python | |
| parent | 038f2a337d09e114469ddcfba5b613cdb8c0fe1d (diff) | |
| download | llvm-cf82700af8c658ae09b14c3d01bb1e73e48d3bd3.zip llvm-cf82700af8c658ae09b14c3d01bb1e73e48d3bd3.tar.gz llvm-cf82700af8c658ae09b14c3d01bb1e73e48d3bd3.tar.bz2 | |
[CodeGenPrepare] Fix isIVIncrement (PR49466)
In the NFC commit 8d835f42a57f15c0b9053bd7c41ea95821a40e5f, the check for `!L` is
moved to a separate function `getIVIncrement` which, instead of using `BO->getParent()`,
uses `PN->getParent()`. However, these two basic blocks are not necessarily the same.
https://bugs.llvm.org/show_bug.cgi?id=49466 demonstrates a case where `PN` is contained in
a loop while `BO` is not, causing the null-pointer dereference in `L->getLoopLatch()`.
This patch checks whether both `BO` and `PN` belong to the same loop before entering `getIVIncrement`.
Reviewed By: mkazantsev
Differential Revision: https://reviews.llvm.org/D98144
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions