Started 13 days ago
Took 5 hr 11 min on green-dragon-02

Failed Build #14365 (Jul 9, 2019 10:16:06 PM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 365594
  • 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/zorg/trunk : 365440
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 365562
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 365576
Changes
  1. Fix modular build issues caused by BitCodes.h

    Consolidate llvm::BWH_* statics into an enum to fix
    module build issues. This fixes the LLVM_Bitcode module,
    getting rid of -Wmodules-ambiguous-internal-linkage.

    Differential Revision: https://reviews.llvm.org/D64469 (detail)
    by Kristina Brooks
  2. [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)
    by maskray
  3. [analyzer] CastValueChecker: Remove a dump()

    Summary: Fix a nit. (detail)
    by charusso
  4. [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)
    by ctopper
  5. [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)
    by rnk
  6. [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)
    by maskray
  7. 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)
    by tstellar
  8. [analyzer] CastValueChecker: Model casts

    Summary:
    It models the LLVM casts:
    - `cast<>`
    - `dyn_cast<>`
    - `cast_or_null<>`
    - `dyn_cast_or_null<>`

    It has a very basic support without checking the `classof()` function.

    (It reapplies the reverted 'llvm-svn: 365582' patch with proper test file.)

    Reviewed By: NoQ

    Tags: #clang

    Differential Revision: https://reviews.llvm.org/D64374 (detail)
    by charusso

Started by timer (6 times)

This run spent:

  • 5 hr 5 min waiting;
  • 5 hr 11 min build duration;
  • 10 hr total from scheduled to completion.
Test Result (5 failures / ±0)Show all failed tests >>>

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

Unexpected pass

This buildbot failed because a test marked as XFAIL unexpectedly passes. This could mean that the cause for the XFAIL is fixed, but it warrants investigation in any case.
Indication 2