[llvm-bugs] [Bug 36590] New: [NewGVN] Assertion "Value number changed after main loop completed!" fails sometimes(!)

[via llvm-bugs]

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

            Bug ID: 36590
           Summary: [NewGVN]  Assertion "Value number changed after main
                    loop completed!" fails sometimes(!)
           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 19995
  --> https://bugs.llvm.org/attachment.cgi?id=19995&action=edit
preprocessed csmith program

This csmith program triggers the assert in NewGVN, but for some reason not
every time! Could this mean an uninitialized variable?

bin/clang -O3 -march=z13 -mllvm -enable-earlycse-memssa=false -mllvm
-enable-gvn-sink -mllvm -enable-loop-versioning-licm -mllvm -vectorize-loops
-mllvm -vectorize-slp -mllvm -enable-newgvn  tc_newgvn_crash.i -o a.out -w

-- 
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/20180303/9a7c7173/attachment.html>