[llvm-bugs] [Bug 26616] wrong code (compiled code hangs) at -O3 on x86_64-linux-gnu

via llvm-bugs llvm-bugs at lists.llvm.org
Fri Feb 19 12:03:22 PST 2016


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

Zhendong Su <su at cs.ucdavis.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WORKSFORME                  |DUPLICATE

--- Comment #4 from Zhendong Su <su at cs.ucdavis.edu> ---
(In reply to comment #3)
> Hi Zhendong,
> llvmlab bisect suggests that this is the same problem as bug 26628:
> 
> $ ./bin/llvmlab bisect --min-rev=260838 --max-rev=261109
> ~/myllvm/build/bin/not /bin/sh -c 'ulimit -t 10; %(path)s/bin/clang -O3 
> 26616.c && ./a.out'
> FAIL: clang-r261099-b17473
> PASS: clang-r260928-b17411
> FAIL: clang-r261004-b17441
> PASS: clang-r260957-b17426
> PASS: clang-r260980-b17434
> FAIL: clang-r260989-b17438
> FAIL: clang-r260985-b17436
> FAIL: clang-r260983-b17435
> clang-r260980-b17434: first working build
> clang-r260983-b17435: next failing build
> 
> Feel free to mark this as a duplicate (one way or the other...since this is
> the earlier report, but that one has some analysis).

Thanks Sanjoy!  Let me mark it as duplicate then.

*** This bug has been marked as a duplicate of bug 26628 ***

-- 
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/20160219/5aeb990d/attachment.html>


More information about the llvm-bugs mailing list