llvm/test/Transforms/LICM/2014-09-10-doFinalizationAssert.ll
David Peixotto cfc42962c8 Fix assertion in LICM doFinalization()
The doFinalization method checks that the LoopToAliasSetMap is
empty. LICM populates that map as it runs through the loop nest,
deleting the entries for child loops as it goes. However, if a child
loop is deleted by another pass (e.g. unrolling) then the loop will
never be deleted from the map because LICM walks the loop nest to
find entries it can delete.

The fix is to delete the loop from the map and free the alias set
when the loop is deleted from the loop nest.

Differential Revision: http://reviews.llvm.org/D5305


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@218387 91177308-0d34-0410-b5e6-96231b3b80d8
2014-09-24 16:48:31 +00:00

31 lines
681 B
LLVM

; RUN: opt < %s -scalar-evolution -licm -loop-unroll -disable-output
; Test triggered an assertion in doFinalization() because loop unroll was deleting
; the inner loop which caused the loop to not get removed from the
; LoopToAliasSetMap.
; Test case taken from test/Transforms/LoopUnroll/unloop.ll.
declare i1 @check() nounwind
define void @skiplevelexit() nounwind {
entry:
br label %outer
outer:
br label %inner
inner:
%iv = phi i32 [ 0, %outer ], [ %inc, %tail ]
%inc = add i32 %iv, 1
call zeroext i1 @check()
br i1 true, label %outer.backedge, label %tail
tail:
br i1 false, label %inner, label %exit
outer.backedge:
br label %outer
exit:
ret void
}