Started 1 mo 3 days ago
Took 48 min on green-dragon-02

Failed Build #14686 (Sep 12, 2019 8:47:04 PM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 371806
  • http://llvm.org/svn/llvm-project/cfe/trunk : 371805
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 371758
  • http://llvm.org/svn/llvm-project/zorg/trunk : 371690
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 371763
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 371773
Changes
  1. [RISCV] Support stack offset exceed 32-bit for RV64

    Differential Revision: https://reviews.llvm.org/D61884 (detail)
    by shiva
  2. For PR17164: split -fno-lax-vector-conversion into three different
    levels:

    -- none: no lax vector conversions [new GCC default]
    -- integer: only conversions between integer vectors [old GCC default]
    -- all: all conversions between same-size vectors [Clang default]

    For now, Clang still defaults to "all" mode, but per my proposal on
    cfe-dev (2019-04-10) the default will be changed to "integer" as soon as
    that doesn't break lots of testcases. (Eventually I'd like to change the
    default to "none" to match GCC and general sanity.)

    Following GCC's behavior, the driver flag -flax-vector-conversions is
    translated to -flax-vector-conversions=integer. (detail)
    by rsmith
  3. AMDGPU/GlobalISel: Legalize G_FFLOOR (detail)
    by arsenm
  4. Temporarily revert r371640 "LiveIntervals: Split live intervals on multiple dead defs".

    It reveals a miscompile on Hexagon. See PR43302 for details. (detail)
    by timshen
  5. AMDGPU/GlobalISel: Legalize G_FMAD

    Unlike SelectionDAG, treat this as a normally legalizable operation.
    In SelectionDAG this is supposed to only ever formed if it's legal,
    but I've found that to be restricting. For AMDGPU this is contextually
    legal depending on whether denormal flushing is allowed in the use
    function.

    Technically we currently treat the denormal mode as a subtarget
    feature, so custom lowering could be avoided. However I consider this
    to be a defect, and this should be contextually dependent on the
    controllable rounding mode of the parent function. (detail)
    by arsenm
  6. Revert r371785.

    r371785 is causing fails on clang-hexagon-elf buildbots. (detail)
    by manojgupta
  7. AMDGPU/GlobalISel: Select G_CTPOP (detail)
    by arsenm
  8. DAG/GlobalISel: Correct type profile of bitcount ops

    The result integer does not need to be the same width as the input.
    AMDGPU, NVPTX, and Hexagon all have patterns working around the types
    matching. GlobalISel defines these as being different type indexes. (detail)
    by arsenm
  9. [libclang] Fix UninstallAbortingLLVMFatalErrorHandler test (detail)
    by Jan Korous
  10. AMDGPU: Add immarg to llvm.amdgcn.init.exec.from.input

    As far as I can tell this has to be a constant. (detail)
    by arsenm
  11. LiveIntervals: Remove assertion

    This testcase is invalid, and caught by the verifier. For the verifier
    to catch it, the live interval computation needs to complete. Remove
    the assert so the verifier catches this, which is less confusing.

    In this testcase there is an undefined use of a subregister, and lanes
    which aren't used or defined. An equivalent testcase with the
    super-register shrunk to have no untouched lanes already hit this
    verifier error. (detail)
    by arsenm
  12. AMDGPU: Inline constant when materalizing FI with add on gfx9

    This was relying on the SGPR usable for the carry out clobber to also
    be used for the input. There was no carry out on gfx9. With no carry
    out clobber to worry about, so the literal can just be directly used
    with a VOP2 add. (detail)
    by arsenm
  13. [Test] Restructure check lines to show differences between modes more clearly

    With the landing of the previous patch (in particular D66318) there are a lot fewer diffs now.  I added an experimental O0 line, and updated all the tests to group experimental and non-experimental O0/O3 together.

    Skimming the remaining diffs, there's only a few which are obviously incorrect.  There's a large number which are questionable, so more todo. (detail)
    by reames
  14. Rename nonvolatile_load/store to simple_load/store [NFC]

    Implement the TODO from D66318. (detail)
    by reames
  15. [AArch64][GlobalISel] Support tail calling with swiftself parameters

    Swiftself uses a callee-saved register. We can tail call when the register used
    in the caller and callee is the same.

    This behaviour is equivalent to that in `TargetLowering::parametersInCSRMatch`.

    Update call-translator-tail-call.ll to verify that we can do this. When we
    support inline assembly, we can write a check similar to the one in the
    general swiftself.ll. For now, we need to verify that we get the correct COPY
    instruction after call lowering.

    Differential Revision: https://reviews.llvm.org/D67511 (detail)
    by paquette
  16. [libclang] Expose abort()-ing LLVM fatal error handler

    Differential Revision: https://reviews.llvm.org/D66775 (detail)
    by Jan Korous
  17. [SDAG] Update generic code to conservatively check for isAtomic in addition to isVolatile

    This is the first sweep of generic code to add isAtomic bailouts where appropriate. The intention here is to have the switch from AtomicSDNode to LoadSDNode/StoreSDNode be close to NFC; that is, I'm not looking to allow additional optimizations at this time. That will come later.  See D66309 for context.

    Differential Revision: https://reviews.llvm.org/D66318 (detail)
    by reames
  18. Add -Wpoison-system-directories warning

    When using clang as a cross-compiler, we should not use system
    headers to do the compilation.
    This CL adds support of a new warning flag -Wpoison-system-directories which
    emits warnings if --sysroot is set and headers from common host system location
    are used.
    By default the warning is disabled.

    The intention of the warning is to catch bad includes which are usually
    generated by third party build system not targeting cross-compilation.
    Such cases happen in Chrome OS when someone imports a new package or upgrade
    one to a newer version from upstream.

    Patch by: denik (Denis Nikitin) (detail)
    by manojgupta

Started by timer (5 times)

This run spent:

  • 4 hr 36 min waiting;
  • 48 min build duration;
  • 5 hr 24 min total from scheduled to completion.

Identified problems

Missing test results

The test result file Jenkins is looking for does not exist after the build.
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