diff options
| author | Justin Bogner <mail@justinbogner.com> | 2016-01-08 19:08:53 +0000 |
|---|---|---|
| committer | Justin Bogner <mail@justinbogner.com> | 2016-01-08 19:08:53 +0000 |
| commit | e9fb228d5920f81417b07a13582945d1f5f472f7 (patch) | |
| tree | cde4605f4e27c68fdf8b7892b64885ad57ed8e4a /llvm/test | |
| parent | 23bcef990e4e3174c80928087b2970d73bb2283f (diff) | |
| download | bcm5719-llvm-e9fb228d5920f81417b07a13582945d1f5f472f7.tar.gz bcm5719-llvm-e9fb228d5920f81417b07a13582945d1f5f472f7.zip | |
LoopInfo: Simplify ownership of Loop objects
It's strange that LoopInfo mostly owns the Loop objects, but that it
defers deleting them to the loop pass manager. Instead, change the
oddly named "updateUnloop" to "markAsRemoved" and have it queue the
Loop object for deletion. We can't delete the Loop immediately when we
remove it, since we need its pointer identity still, so we'll mark the
object as "invalid" so that clients can see what's going on.
llvm-svn: 257191
Diffstat (limited to 'llvm/test')
| -rw-r--r-- | llvm/test/Transforms/LoopUnroll/unloop.ll | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/llvm/test/Transforms/LoopUnroll/unloop.ll b/llvm/test/Transforms/LoopUnroll/unloop.ll index b98b4a3fffb..720b2ae1bdb 100644 --- a/llvm/test/Transforms/LoopUnroll/unloop.ll +++ b/llvm/test/Transforms/LoopUnroll/unloop.ll @@ -1,6 +1,6 @@ ; RUN: opt < %s -S -loop-unroll -verify-loop-info | FileCheck %s ; -; Unit tests for LoopInfo::updateUnloop. +; Unit tests for LoopInfo::markAsRemoved. declare i1 @check() nounwind |
