Started 3 mo 12 days ago
Took 2 hr 57 min on green-dragon-15

Failed Build #4164 (Jul 9, 2019 8:21:04 PM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 365589
  • http://llvm.org/svn/llvm-project/cfe/trunk : 365590
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 365591
  • http://llvm.org/svn/llvm-project/lld/trunk : 365553
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 364589
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 365562
  • http://llvm.org/svn/llvm-project/test-suite/trunk : 364448
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 365576
  • http://llvm.org/svn/llvm-project/polly/trunk : 365470
Changes
  1. [ubsan][test] Restore float-divide-by-zero test

    Removed by rCTE365307 to fix buildbots. It can be restored now because D64317/rC365587 brought back -fsanitize=float-divide-by-zero (detail/ViewSVN)
    by maskray
  2. [analyzer] CastValueChecker: Remove a dump()

    Summary: Fix a nit. (detail/ViewSVN)
    by charusso
  3. [X86] Limit getTargetConstantFromNode to only work on NormalLoads not extending loads.

    This seems to fix a failure reported by Jordan Rupprecht, but we
    don't have a reduced test case yet. (detail/ViewSVN)
    by ctopper
  4. [Support] Move llvm::MemoryBuffer to sys::fs::file_t

    Summary:
    On Windows, Posix integer file descriptors are a compatibility layer
    over native file handles provided by the C runtime. There is a hard
    limit on the maximum number of file descriptors that a process can open,
    and the limit is 8192. LLD typically doesn't run into this limit because
    it opens input files, maps them into memory, and then immediately closes
    the file descriptor. This prevents it from running out of FDs.

    For various reasons, I'd like to open handles to every input file and
    keep them open during linking. That requires migrating MemoryBuffer over
    to taking open native file handles instead of integer FDs.

    Reviewers: aganea, Bigcheese

    Reviewed By: aganea

    Subscribers: smeenai, silvas, mehdi_amini, hiraditya, steven_wu, dexonsmith, dang, llvm-commits, zturner

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D63453 (detail/ViewSVN)
    by rnk
  5. [Driver] Add float-divide-by-zero back to supported sanitizers after D63793/rC365272

    D63793 removed float-divide-by-zero from the "undefined" set but it
    failed to add it to getSupportedSanitizers(), thus the sanitizer is
    rejected by the driver:

        clang-9: error: unsupported option '-fsanitize=float-divide-by-zero' for target 'x86_64-unknown-linux-gnu'

    Also, add SanitizerMask::FloatDivideByZero to a few other masks to make -fsanitize-trap, -fsanitize-recover, -fsanitize-minimal-runtime and -fsanitize-coverage work.

    Reviewed By: rsmith, vitalybuka

    Differential Revision: https://reviews.llvm.org/D64317 (detail/ViewSVN)
    by maskray
  6. AMDGPU/GlobalISel: Add support for wide loads >= 256-bits

    Summary:
    This adds support for the most commonly used wide load types:
    <8xi32>, <16xi32>, <4xi64>, and <8xi64>

    Reviewers: arsenm

    Reviewed By: arsenm

    Subscribers: hiraditya, kzhuravl, jvesely, wdng, nhaehnle, yaxunl, rovka, kristof.beyls, dstuttard, tpr, t-tye, volkan, Petar.Avramovic, llvm-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D57399 (detail/ViewSVN)
    by tstellar

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

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

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

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

This run spent:

  • 1 hr 48 min waiting;
  • 2 hr 57 min build duration;
  • 4 hr 46 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