Started 1 mo 0 days ago
Took 8 min 25 sec on green-dragon-08

Failed Build #5537 (Oct 14, 2019 1:17:47 AM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 374755
  • http://llvm.org/svn/llvm-project/cfe/trunk : 374756
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 374612
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 364589
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 374723
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 374753
Changes
  1. [docs] loop pragmas: options implying transformations

    Following our discussion on the cfe dev list:
    http://lists.llvm.org/pipermail/cfe-dev/2019-August/063054.html,
    I have added a paragraph that is explicit about loop pragmas, and
    transformation options implying the corresponding transformation.

    Differential Revision: https://reviews.llvm.org/D66199 (detail/ViewSVN)
    by sjoerdmeijer
  2. [X86] Teach EmitTest to handle ISD::SSUBO/USUBO in order to use the Z flag from the subtract directly during isel.

    This prevents isel from emitting a TEST instruction that
    optimizeCompareInstr will need to remove later.

    In some of the modified tests, the SUB gets duplicated due to
    the flags being needed in two places and being clobbered in
    between. optimizeCompareInstr was able to optimize away the TEST
    that was using the result of one of them, but optimizeCompareInstr
    doesn't know to turn SUB into CMP after removing the TEST. It
    only knows how to turn SUB into CMP if the result was already
    dead.

    With this change the TEST never exists, so optimizeCompareInstr
    doesn't have to remove it. Then it can just turn the SUB into
    CMP immediately.

    Fixes PR43649. (detail/ViewSVN)
    by ctopper

Started by upstream project Clang Stage 2: cmake, R -g Tsan, using Stage 1 RA build number 18512
originally caused by:

This run spent:

  • 6.6 sec waiting;
  • 8 min 25 sec build duration;
  • 8 min 32 sec total from scheduled to completion.

Identified problems

Ninja target failed

Below is a link to the first failed ninja target.
Indication 1

Missing test results

The test result file Jenkins is looking for does not exist after the build.
Indication 2

Compile Error

This build failed because of a compile error. Below is a list of all errors in the build log:
Indication 3