[llvm-bugs] [Bug 35839] New: assertion failure in NewGVN: Value number changed after main loop completed
via llvm-bugs
llvm-bugs at lists.llvm.org
Fri Jan 5 18:42:50 PST 2018
https://bugs.llvm.org/show_bug.cgi?id=35839
Bug ID: 35839
Summary: assertion failure in NewGVN: Value number changed
after main loop completed
Product: libraries
Version: 6.0
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: Scalar Optimizations
Assignee: unassignedbugs at nondot.org
Reporter: superjoe30 at gmail.com
CC: llvm-bugs at lists.llvm.org
This is latest release_60 revisions as of this morning:
LLVM r321742
clang r321788
clang -c -O3 -mllvm -enable-newgvn bad.ll
clang-6.0:
/home/andy/Downloads/llvm_release_60/lib/Transforms/Scalar/NewGVN.cpp:3285:
void {anonymous}::NewGVN::verifyIterationSettled(llvm::Function&): Assertion
`BeforeCC->isEquivalentTo(AfterCC) && "Value number changed after main loop
completed!"' failed.
I'll work on getting the IR smaller.
--
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/20180106/99f18147/attachment.html>
More information about the llvm-bugs
mailing list