Started 11 days ago
Took 4 hr 56 min on green-dragon-02

Failed Build #14188 (Jun 7, 2019 8:05:47 PM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 362864
  • http://llvm.org/svn/llvm-project/cfe/trunk : 362856
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 362859
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 362745
  • http://llvm.org/svn/llvm-project/zorg/trunk : 362851
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 362865
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 362811
Changes
  1. Substantially reduce instantiations and debug size of std::function

    std::function uses a standard allocator to manage its memory, however
    standard allocators are templates and using them correctly requires
    a stupid amount of instantiations. This leads to a substantial increase
    in debug info and object sizes.

    This patch addresses the issue by dropping the allocator when possible
    and using raw new and delete to get memory.

    This change decreases the object file size for the test func.wrap.func.con/F.pass.cpp by 33% and the final binary by 29% (when compiled with -g -ggnu-pubnames -gpubnames).

    It also roughly halfs the number of entries in the pubnames and pubtype
    sections. (detail)
    by ericwf
  2. gn build: Merge r362857 (detail)
    by nico
  3. [llvm-objcopy][MachO] Recompute and update offset/size fields in the writer

    Summary:
    Recompute and update offset/size fields so that we can implement llvm-objcopy options like --only-section.

    This patch is the first step and focuses on supporting load commands that covered by existing tests: executable files and
    dynamic libraries are not supported.

    Reviewers: alexshap, rupprecht, jhenderson

    Reviewed By: alexshap, rupprecht

    Subscribers: compnerd, jakehehrlich, llvm-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D62652 (detail)
    by seiya
  4. Fix some incorrect std::function tests (detail)
    by ericwf
  5. Visualizer for APInt and remove obsolete visualizer

    Visualizer for the simple case of APInt (uints < 2^64)
    as will be required  for Clang ConstantArrayType visualizer.
    Also, removed obsolete VS2013 SmallVectorVisualizer as VS2013
    is no longer supported. (detail)
    by mps
  6. Experimantal dfsan mode "fast16labels=1"

    Summary:
    dfsan mode "fast16labels=1".
    In this mode the labels are treated as 16-bit bit masks.

    Reviewers: pcc

    Reviewed By: pcc

    Subscribers: delcypher, #sanitizers, llvm-commits

    Tags: #llvm, #sanitizers

    Differential Revision: https://reviews.llvm.org/D62870 (detail)
    by kcc
  7. Factor out SelectionDAG's switch analysis and lowering into a separate component.

    In order for GlobalISel to re-use the significant amount of analysis and
    optimization code in SDAG's switch lowering, we first have to extract it and
    create an interface to be used by both frameworks.

    No test changes as it's NFC.

    Differential Revision: https://reviews.llvm.org/D62745 (detail)
    by aemerson
  8. DebugInfo: Add support for 'nodebug' attribute on typedefs and alias templates

    Seems like a logical extension to me - and of interest because it might
    help reduce the debug info size of libc++ by applying this attribute to
    type traits that have a disproportionate debug info cost compared to the
    benefit (& possibly harm/confusion) they cause users. (detail)
    by dblaikie
  9. [analyzer] Add werror flag for analyzer warnings

    Summary:
    We're using the clang static analyzer together with a number of
    custom analyses in our CI system to ensure that certain invariants
    are statiesfied for by the code every commit. Unfortunately, there
    currently doesn't seem to be a good way to determine whether any
    analyzer warnings were emitted, other than parsing clang's output
    (or using scan-build, which then in turn parses clang's output).
    As a simpler mechanism, simply add a `-analyzer-werror` flag to CC1
    that causes the analyzer to emit its warnings as errors instead.
    I briefly tried to have this be `Werror=analyzer` and make it go
    through that machinery instead, but that seemed more trouble than
    it was worth in terms of conflicting with options to the actual build
    and special cases that would be required to circumvent the analyzers
    usual attempts to quiet non-analyzer warnings. This is simple and it
    works well.

    Reviewed-By: NoQ, Szelethusw
    Differential Revision: https://reviews.llvm.org/D62885 (detail)
    by kfischer
  10. LoopDistribute: Add testcase where SCEV wants to insert a runtime
    check.

    Only the memory based checks were being tested. Prepare for fix in
    convergent handling. (detail)
    by arsenm
  11. [GVN] non-functional code movement

    Summary: Move some code around, in preparation for later fixes
    to the non-integral addrspace handling (D59661)

    Patch By Jameson Nash <jameson@juliacomputing.com>

    Reviewed By: reames, loladiro
    Differential Revision: https://reviews.llvm.org/D59729 (detail)
    by kfischer
  12. AMDGPU: Force skips around traps (detail)
    by arsenm
  13. Removed long time off-line builders and slaves.

    Builders:
    llvm-mips-linux
    perf-x86_64-penryn-O3
    clang-openbsd-amd64
    perf-x86_64-penryn-O3-polly-fast
    perf-x86_64-penryn-O3-polly-parallel-fast
    perf-x86_64-penryn-O3-polly-unprofitable
    perf-x86_64-penryn-O3-polly
    perf-x86_64-penryn-O3-polly-detect-only
    lldb-amd64-ninja-freebsd11
    clang-native-aarch64-full
    clang-bpf-build

    Slaves:
    pollyperf1, pollyperf2, pollyperf3, pollyperf4, pollyperf5, pollyperf6, pollyperf7, pollyperf11, pollyperf14, pollyperf15,
    mipsswbrd002, juno-aarch64-01, bpf-build-slave01, lldb-amd64-ninja-freebsd11, openbsd-amd64 (detail)
    by gkistanova
  14. Removed commented out builders and slaves. (detail)
    by gkistanova

Started by timer (5 times)

This run spent:

  • 4 hr 54 min waiting;
  • 4 hr 56 min build duration;
  • 9 hr 51 min total from scheduled to completion.
Test Result (1 failure / -1)

Identified problems

Compile Error

This build failed because of a compile error. 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

Regression test failed

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