[llvm-bugs] [Bug 35074] New: [NewGVN] Assertion `BeforeCC->isEquivalentTo(AfterCC) && "Value number changed after main loop completed!"' failed

via llvm-bugs llvm-bugs at lists.llvm.org
Wed Oct 25 08:44:45 PDT 2017


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

            Bug ID: 35074
           Summary: [NewGVN] Assertion `BeforeCC->isEquivalentTo(AfterCC)
                    && "Value number changed after main loop completed!"'
                    failed
           Product: libraries
           Version: trunk
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: Scalar Optimizations
          Assignee: unassignedbugs at nondot.org
          Reporter: mcrosier at codeaurora.org
                CC: llvm-bugs at lists.llvm.org

Likely a duplicate of PR34479 and PR34482, but can be reproduced without polly.

Test.cpp:
class A {
  void m_fn1();
  void m_fn2(signed);
  int mapmaxx;
};
void A::m_fn1() {
  int y, a;
  y = 1;
  for (;; y++)
    for (; mapmaxx;) {
      a = y - 1;
      for (; a <= y + 1; a++)
        m_fn2(a);
    }
}

Reproduce with:
clang -O3 -mllvm -enable-newgvn test.cpp -o - -S

-- 
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/20171025/06bacbdf/attachment.html>


More information about the llvm-bugs mailing list