[llvm-bugs] [Bug 38778] simple-loop-unswitch asserts after nontrivial unswitch: Assertion `use_empty() && "Uses remain when a value is destroyed!"' failed.

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=38778

Fedor Sergeev <fedor.v.sergeev at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #9 from Fedor Sergeev <fedor.v.sergeev at gmail.com> ---
Fixed by:

commit 8b6effd9690024d8138de9c903d88a0c3f706487
Author: Fedor Sergeev <fedor.sergeev at azul.com>
Date:   Tue Sep 4 20:19:41 2018 +0000

    [SimpleLoopUnswitch] remove a chain of dead blocks at once

    Recent change to deleteDeadBlocksFromLoop was not enough to
    fix all the problems related to dead blocks after nontrivial
    unswitching of switches.

    We need to delete all the dead blocks that were created during
    unswitching, otherwise we will keep having problems with phi's
    or dead blocks.

    This change removes all the dead blocks that are reachable from the loop,
    not trying to track whether these blocks are newly created by unswitching
    or not. While not completely correct, we are unlikely to get loose but
    reachable dead blocks that do not belong to our loop nest.

    It does fix all the failures currently known, in particular PR38778.

    Reviewed By: asbirlea
    Differential Revision: https://reviews.llvm.org/D51519

    llvm-svn: 341398

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20190701/c90cae6e/attachment.html>