[llvm-bugs] [Bug 30244] New: TSAN analyze step fails on the bots

[via llvm-bugs]

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

            Bug ID: 30244
           Summary: TSAN analyze step fails on the bots
           Product: compiler-rt
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: compiler-rt
          Assignee: unassignedbugs at nondot.org
          Reporter: krasin at google.com
                CC: llvm-bugs at lists.llvm.org
    Classification: Unclassified

Recently, the sanitizer autoconf bot turned red:
http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-autoconf/builds/24680/steps/tsan%20analyze/logs/stdio

The failure is described as:

+
/mnt/b/sanitizer-buildbot4/sanitizer-x86_64-linux-autoconf/build/llvm/projects/compiler-rt/lib/tsan/check_analyze.sh
/tmp/tsan_exe.L3wvOKAx
...
     read1 tot 412; size 1428; rsp 1; push 6; pop 6; call 2; load  6; store 11;
sh  28; mov  95; lea   8; cmp  60
...
FAILED read1 must contain push 5
+ echo @@@STEP_FAILURE@@@
@@@STEP_FAILURE@@@

On the previous buildbot run, it was 5:
http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-autoconf/builds/24679/steps/tsan%20analyze/logs/stdio

     read2 tot 386; size 1361; rsp 1; push 5; pop 5; call 2; load  8; store 11;
sh  28; mov  89; lea   4; cmp  64

The CL affected the code is (unsurprisingly) related to codegen:
https://reviews.llvm.org/rL280364

And the last commit to check_analyze.sh tells us:

"""
r268382 | dvyukov | 2016-05-03 06:59:41 -0700 (Tue, 03 May 2016) | 11 lines

tsan: update tsan_analyze to what tip clang generates

We used to depend on host gcc. But some distributions got
new gcc recently which broke the check. Generally, we can't
depend that an arbitrary host gcc generates something stable.

Switch to clang.
This has an additional advantage of catching regressions in
clang codegen.
"""

I guess, we have caught a regression in clang codegen, but I am failing to
decipher what it means for us: shall we fix the codegen or just update the
expectation?

-- 
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/20160901/26bc41ba/attachment.html>