diff options
author | Chijun Sima <simachijun@gmail.com> | 2018-07-25 06:18:33 +0000 |
---|---|---|
committer | Chijun Sima <simachijun@gmail.com> | 2018-07-25 06:18:33 +0000 |
commit | bd5d80d050567c9f9a84e32e46f02496958c414e (patch) | |
tree | fa727795cd71d6372cb1b138480306102e850da5 /llvm/tools/llvm-readobj/llvm-readobj.cpp | |
parent | dc0e8a601dae520e6f05cd18b7dc88b6aaf9ebe1 (diff) | |
download | bcm5719-llvm-bd5d80d050567c9f9a84e32e46f02496958c414e.tar.gz bcm5719-llvm-bd5d80d050567c9f9a84e32e46f02496958c414e.zip |
[Dominators] Assert if there is modification to DelBB while it is awaiting deletion
Summary:
Previously, passes use
```
DomTreeUpdater DTU(DT, DomTreeUpdater::UpdateStrategy::Lazy);
DTU.deleteBB(DelBB);
```
to delete a BasicBlock.
But passes which don't have the ability to update DomTree (e.g. tailcallelim, simplifyCFG) cannot recognize a DelBB awaiting deletion and will continue to process this DelBB.
This is a simple approach to notify devs of passes which may use DTU in the future to deal with deleted BasicBlocks under Lazy Strategy correctly.
Reviewers: kuhar, brzycki, dmgreen
Reviewed By: kuhar
Subscribers: llvm-commits
Differential Revision: https://reviews.llvm.org/D49731
llvm-svn: 337891
Diffstat (limited to 'llvm/tools/llvm-readobj/llvm-readobj.cpp')
0 files changed, 0 insertions, 0 deletions