[llvm-bugs] [Bug 36501] New: [NewGVN] Assertion "Value number changed after main loop completed!" failed

[via llvm-bugs]

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

            Bug ID: 36501
           Summary: [NewGVN]  Assertion "Value number changed after main
                    loop completed!" failed
           Product: libraries
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: Scalar Optimizations
          Assignee: unassignedbugs at nondot.org
          Reporter: paulsson at linux.vnet.ibm.com
                CC: llvm-bugs at lists.llvm.org

Created attachment 19949
  --> https://bugs.llvm.org/attachment.cgi?id=19949&action=edit
reduced testcase

bin/opt -mtriple=s390x-linux-gnu -mcpu=z13 tc_newgvn_aftermainloop.ll -o
out.opt -tbaa -loop-rotate -licm -loop-unswitch -simplifycfg -instcombine
-loop-unroll -newgvn

opt: /home/ijonpan/llvm/llvm-dev-2/lib/Transforms/Scalar/NewGVN.cpp:3285: void
{anonymous}::NewGVN::verifyIterationSettled(llvm::Function&): Assertion
`BeforeCC->isEquivalentTo(AfterCC) && "Value number changed after main loop
completed!"' failed.
#0 0x0000000002cb51e0 llvm::sys::PrintStackTrace(llvm::raw_ostream&)
(bin/opt+0x2cb51e0)
...

-- 
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/20180224/90478e5d/attachment-0001.html>