aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.cpp
diff options
context:
space:
mode:
authorNikita Popov <nikita.ppv@gmail.com>2021-10-30 21:40:14 +0200
committerNikita Popov <nikita.ppv@gmail.com>2021-11-27 12:37:15 +0100
commit2b160e95c89f28a30e2481e6131073659d866a8c (patch)
tree156ada86e0cc420cba2452bc9d3163d1bc0ae3e6 /lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.cpp
parentda66263b6e505a4c605efbe8d68c3b09ad3606a4 (diff)
downloadllvm-2b160e95c89f28a30e2481e6131073659d866a8c.zip
llvm-2b160e95c89f28a30e2481e6131073659d866a8c.tar.gz
llvm-2b160e95c89f28a30e2481e6131073659d866a8c.tar.bz2
Reland [SCEV] Fix and validate ValueExprMap/ExprValueMap consistency
Relative to the previous landing attempt, this introduces an additional flag on forgetMemoizedResults() to not remove SCEVUnknown phis from the value map. The invalidation after BECount calculation wants to leave these alone and skips them in its own use-def walk, but we can still end up invalidating them via forgetMemoizedResults() if there is another IR value with the same SCEV. This is intended as a temporary workaround only, and the need for this should go away once the getBackedgeTakenInfo() invalidation is refactored in the spirit of D114263. ----- This adds validation for consistency of ValueExprMap and ExprValueMap, and fixes identified issues: * Addrec construction directly wrote to ValueExprMap in a few places, without updating ExprValueMap. Add a helper to ensures they stay consistent. The adjustment in forgetSymbolicName() explicitly drops the old value from the map, so that we don't rely on it being overwritten. * forgetMemoizedResultsImpl() was dropping the SCEV from ExprValueMap, but not dropping the corresponding entries from ValueExprMap. Differential Revision: https://reviews.llvm.org/D113349
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.cpp')
0 files changed, 0 insertions, 0 deletions