Started 7 days 4 hr ago
Took 1 hr 16 min on green-dragon-20

Failed Build rL:371775 - C:371767 - #567 (Sep 12, 2019 2:31:05 PM)

  • : 371775
  • : 371767
  • : 371758
  • : 364589
  • : 371690
  • : 371763
  • : 371773
  1. [DAGCombiner][X86] Pass the CmpOpVT to reduceSelectOfFPConstantLoads so X86 can exclude fp128 compares.

    The X86 decision assumes the compare will produce a result in an XMM
    register, but that can't happen for an fp128 compare since those
    go to a libcall the returns an i32. Pass the VT so X86 can check
    the type. (detail/ViewSVN)
    by ctopper
  2. [ConstantFolding] Expand folding of some library functions

    Expanding the folding of `nearbyint()`, `rint()` and `trunc()` to library
    functions, in addition to the current support for intrinsics.

    Differential revision: (detail/ViewSVN)
    by evandro
  3. [ClangTidy] Adjust the name getCheckName to getCheckerName due to API change. (detail/ViewSVN)
    by timshen
  4. Fix llvm-reduce tests so that they don't assume the source code is

    Instead of copying over the original file permissions, just create
    a new file and add the executable bit. (detail/ViewSVN)
    by timshen
  5. [SelectionDAGBuilder] Simplify loop in visitSelect back to how it was before r255558.

    This code was changed to accomodate fp128 being softened to itself
    during type legalization on x86-64. This was done in order to create
    libcalls while having fp128 as a legal type. We're now doing the
    libcall creation during LegalizeDAG and the type legalization changes
    to enable the old behavior have been removed. So this change to
    SelectionDAGBuilder is no longer needed. (detail/ViewSVN)
    by ctopper

Started by an SCM change (5 times)

This run spent:

  • 49 min waiting;
  • 1 hr 16 min build duration;
  • 2 hr 5 min total from scheduled to completion.
LLVM/Clang Warnings: 2 warnings.
Test Result (1 failure / +1)

Identified problems

Regression test failed

This build failed because a regression test in the test suite FAILed. See the test report for details.
Indication 1

Ninja target failed

Below is a link to the first failed ninja target.
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