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: unassignedb...@nondot.org
Reporter: pauls...@linux.vnet.ibm.com
CC: llvm-bugs@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._______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
