Started 12 days ago
Took 4 hr 56 min on green-dragon-19

Success Build #18191 (Jun 11, 2019 9:45:07 PM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 363120
  • http://llvm.org/svn/llvm-project/cfe/trunk : 363116
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 363104
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 362745
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 363117
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 363068
Changes
  1. [RISCV] Add CFI directives for RISCV prologue/epilog.

    In order to generate correct debug frame information, it needs to
    generate CFI information in prologue and epilog.

    Differential Revision: https://reviews.llvm.org/D61773 (detail/ViewSVN)
    by hsiangkai
  2. [NFC] Correct comments in RegisterCoalescer.

    Differential Revision: https://reviews.llvm.org/D63124 (detail/ViewSVN)
    by hsiangkai
  3. [PowerPC][NFC] Added test for sext/shl combination after isel. (detail/ViewSVN)
    by lkail
  4. Apply [[nodebug]] to typedefs throughout the STL.

    When applied to a typedef or alias template, the [[nodebug]] attribute
    makes the typedef transparent to the debugger, so instead of seeing
    `std::__function::__alloc_func<remove_reference<void(&)()>::type,
    allocator<remove_reference<void(&)()>, void()>::_Target` you see
    `void(&)()` as the type of the variable in your debugger.

    Removing all this SFINAE noise from debug info has huge binary size
    wins, in addition to improving the readability.

    For now this change is on by default. Users can override it by
    specifying -D_LIBCPP_NODEBUG_TYPE= (detail/ViewSVN)
    by ericwf
  5. [X86] [ABI] Fix i386 ABI "__m64" type bug

    According to System V i386 ABI: the  __m64 type paramater and return
    value are passed by MMX registers. But current implementation treats
    __m64 as i64 which results in parameter passing by stack and returning
    by EDX and EAX.

    This patch fixes the bug (https://bugs.llvm.org/show_bug.cgi?id=41029)
    for Linux and NetBSD.

    Patch by Wei Xiao (wxiao3)

    Differential Revision: https://reviews.llvm.org/D59744 (detail/ViewSVN)
    by pengfei
  6. [NFC][CodeGen] Add unary FNeg tests to X86/avx512vl-intrinsics-fast-isel.ll X86/combine-fabs.ll

    X86/avx512vl-intrinsics-fast-isel.ll is only partially complete. (detail/ViewSVN)
    by mcinally
  7. Mark declarations as referenced by a default argument in a
    potentially-evaluated context.

    This applies even if the use of the default argument is within an
    unevaluated context. (detail/ViewSVN)
    by rsmith
  8. Fix a bug in getSCEVAtScope w.r.t. non-canonical loops

    The issue is that if we have a loop with multiple predecessors outside the loop, the code was expecting to merge them and only return if equal, but instead returned the first one seen.

    I have no idea if this actually tripped anywhere.  I noticed it by accident when reading the code and have no idea how to go about constructing a test case. (detail/ViewSVN)
    by reames
  9. Move libc++ specific tests for std::function out of the std directory (detail/ViewSVN)
    by ericwf
  10. Add documentation and tests for Clangs C++11 extensions in C++03.

    As we gear up to drop support for GCC in C++03, we should make clear
    what our C++03 mode is, the C++11 extensions it provides,
    and the C++11 extensions it depends on.

    The section of this document discussing user-facing extensions has
    been left blank while the community discusses new directions. For now
    it's just a warning to users.

    Additionally, the document contains examples of how these extensions
    should be used and why. For example, using alias templates over class
    templates. (detail/ViewSVN)
    by ericwf

Started by upstream project clang-stage2-Rthinlto_relay build number 1597
originally caused by:

This run spent:

  • 3 ms waiting;
  • 4 hr 56 min build duration;
  • 4 hr 56 min total from scheduled to completion.
Cobol Warnings: 0 warnings.
  • No warnings since build 10,378.
  • New zero warnings highscore: no warnings for 378 days!
Test Result (no failures)