[llvm-bugs] [Bug 42682] New: LoopSafetyInfo::allLoopPathsLeadToBlock ignores potential endless loops

[via llvm-bugs]

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

            Bug ID: 42682
           Summary: LoopSafetyInfo::allLoopPathsLeadToBlock ignores
                    potential endless loops
           Product: libraries
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: Core LLVM classes
          Assignee: unassignedbugs at nondot.org
          Reporter: jdoerfert at anl.gov
                CC: llvm-bugs at lists.llvm.org

Created attachment 22259
  --> https://bugs.llvm.org/attachment.cgi?id=22259&action=edit
reproducer

The attached reproducer shows how SimpleLoopSafetyInfo::isGuaranteedToExecute()
assumes the store 7 is executed even though it could be dead if the value of c
(%arg) is 0. The problem seems to be in LoopSafetyInfo::allLoopPathsLeadToBlock
though. I have not investigated if any transformations that use this interface
are potentially using wrong information.

-- 
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/20190719/c23edf55/attachment.html>