Started 5 mo 2 days ago
Took 2 hr 57 min on green-dragon-14

Failed Build #4159 (Jul 9, 2019 3:31:40 AM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 365456
  • http://llvm.org/svn/llvm-project/cfe/trunk : 365454
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 365424
  • http://llvm.org/svn/llvm-project/lld/trunk : 365443
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 364589
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 365359
  • http://llvm.org/svn/llvm-project/test-suite/trunk : 364448
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 365460
  • http://llvm.org/svn/llvm-project/polly/trunk : 363599
Changes
  1. Fixed assertion (detail/ViewSVN)
    by sureyeaah
  2. [SelectionDAG] Simplify some calls to getSetCCResultType. NFC

    DAGTypeLegalizer and SelectionDAGLegalize has helper
    functions wrapping the call to TLI.getSetCCResultType(...).
    Use those helpers in more places. (detail/ViewSVN)
    by bjope
  3. [LegalizeTypes] Fix saturation bug for smul.fix.sat

    Summary:
    Make sure we use SETGE instead of SETGT when checking
    if the sign bit is zero at SMULFIXSAT expansion.

    The faulty expansion occured when doing "expand" of
    SMULFIXSAT and the scale was exactly matching the
    size of the smaller type. For example doing
      i64 Z = SMULFIXSAT X, Y, 32
    and expanding X/Y/Z into using two i32 values.

    The problem was that we sometimes did not saturate
    to min when overflowing.

    Here is an example using Q3.4 numbers:

    Consider that we are multiplying X and Y.
      X = 0x80 (-8.0 as Q3.4)
      Y = 0x20 (2.0 as Q3.4)
    To avoid loss of precision we do a widening
    multiplication, getting a 16 bit result
      Z = 0xF000 (-16.0 as Q7.8)

    To detect negative overflow we should check if
    the five most significant bits in Z are less than -1.
    Assume that we name the 4 most significant bits
    as HH and the next 4 bits as HL. Then we can do the
    check by examining if
    (HH < -1) or (HH == -1 && "sign bit in HL is zero").

    The fault was that we have been doing the check as
    (HH < -1) or (HH == -1 && HL > 0)
    instead of
    (HH < -1) or (HH == -1 && HL >= 0).

    In our example HH is -1 and HL is 0, so the old
    code did not trigger saturation and simply truncated
    the result to 0x00 (0.0). With the bugfix we instead
    detect that we should saturate to min, and the result
    will be set to 0x80 (-8.0).

    Reviewers: leonardchan, bevinh

    Reviewed By: leonardchan

    Subscribers: hiraditya, llvm-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D64331 (detail/ViewSVN)
    by bjope
  4. Retire VS2015 Support

    As proposed here: https://lists.llvm.org/pipermail/llvm-dev/2019-June/133147.html

    This patch raises the minimum supported version to build LLVM/Clang to Visual Studio 2017.

    Differential Revision: https://reviews.llvm.org/D64326 (detail/ViewSVN)
    by rksimon
  5. dummy variable extraction on a function scope

    Summary:
    - Added extraction to a dummy variable
    - using auto for the dummy variable type for now
    - Works on a function scope
    - Adding braces to create a compound statement not supported yet
    - added unit tests

    Reviewers: sammccall, kadircet

    Subscribers: mgorny, jkorous, arphaman, cfe-commits

    Tags: #clang

    Differential Revision: https://reviews.llvm.org/D63773 (detail/ViewSVN)
    by sureyeaah
  6. Retire VS2015 Support

    As proposed here: https://lists.llvm.org/pipermail/llvm-dev/2019-June/133147.html

    This patch raises the minimum supported version to build LLVM/Clang to Visual Studio 2017.

    Differential Revision: https://reviews.llvm.org/D64326 (detail/ViewSVN)
    by rksimon
  7. [docs][llvm-dwarfdump] Make some option descriptions clearer and more precise

    Some of the wording in the doc (taken largely from the help text), was a
    little imprecise in some cases, so this patch makes it a little more
    precise.

    Reviewed by: JDevlieghere, probinson

    Differential Revision: https://reviews.llvm.org/D64332 (detail/ViewSVN)
    by jhenderson
  8. [llvm-profdata] Don't make the output overwrite the input file.

    Some file systems may not allow this behavior, the test fails on our internal
    system ("Permission denied"). (detail/ViewSVN)
    by hokein
  9. Fixing @llvm.memcpy not honoring volatile.
    This is explicitly not addressing target-specific code, or calls to memcpy.

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

    Reviewers: courbet

    Subscribers: hiraditya, llvm-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D63215 (detail/ViewSVN)
    by gchatelet
  10. Revert r364515 and r364524

    Jordan reports on llvm-commits a performance regression with r364515,
    backing the patch out while it's investigated. (detail/ViewSVN)
    by jmorse
  11. [NFC][PowerPC] Added a test to show current codegen of MachinePRE (detail/ViewSVN)
    by lkail

Started by upstream project SVN: Clang Stage 1: cmake, RA, using system compiler build number 57817
originally caused by:

Started by upstream project SVN: Clang Stage 1: cmake, RA, using system compiler build number 57818
originally caused by:

This run spent:

  • 55 min waiting;
  • 2 hr 57 min build duration;
  • 3 hr 52 min total from scheduled to completion.

Identified problems

Assertion failure

This build failed because of an assertion failure. Below is a list of all errors in the build log:
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