Started 2 mo 25 days ago
Took 1 hr 15 min on green-dragon-20

Success Build rL:371868 - C:371859 - #581 (Sep 13, 2019 9:32:16 AM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 371868
  • http://llvm.org/svn/llvm-project/cfe/trunk : 371859
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 371822
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 364589
  • http://llvm.org/svn/llvm-project/zorg/trunk : 371835
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 371867
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 371773
Changes
  1. [AArch64][GlobalISel] Add support for sibcalling callees with varargs

    This adds support for tail calling callees with varargs, equivalent to how it
    is done in AArch64ISelLowering.

    This only works for sibling calls, and does not add the necessary support for
    musttail with varargs. (See r345641 for equivalent ISelLowering support.) This
    should be implemented when we stop falling back on musttail.

    Update call-translator-tail-call.ll to show that we can now tail call varargs.

    Differential Revision: https://reviews.llvm.org/D67518 (detail/ViewSVN)
    by paquette
  2. Recommit r370502: Make `vector` unconditionally move elements when
    exceptions are disabled.

    The patch was reverted due to some confusion about non-movable types. ie
    types
    that explicitly delete their move constructors. However, such types do
    not meet
    the requirement for `MoveConstructible`, which is required by
    `std::vector`:

    Summary:

    `std::vector<T>` is free choose between using copy or move operations
    when it
    needs to resize. The standard only candidates that the correct exception
    safety
    guarantees are provided. When exceptions are disabled these guarantees
    are
    trivially satisfied. Meaning vector is free to optimize it's
    implementation by
    moving instead of copying.

    This patch makes `std::vector` unconditionally move elements when
    exceptions are
    disabled. This optimization is conforming according to the current
    standard wording.

    There are concerns that moving in `-fno-noexceptions`mode will be a
    surprise to
    users. For example, a user may be surprised to find their code is slower
    with
    exceptions enabled than it is disabled. I'm sympathetic to this
    surprised, but
    I don't think it should block this optimization.

    Reviewers: mclow.lists, ldionne, rsmith
    Reviewed By: ldionne
    Subscribers: zoecarver, christof, dexonsmith, libcxx-commits
    Tags: #libc
    Differential Revision: https://reviews.llvm.org/D62228 (detail/ViewSVN)
    by ericwf
  3. [yaml2obj/ObjectYAML] - Cleanup the error reporting API, add custom errors handlers.

    This is a continuation of the YAML library error reporting
    refactoring/improvement and the idea by itself was mentioned
    in the following thread:
    https://reviews.llvm.org/D67182?id=218714#inline-603404

    This performs a cleanup of all object emitters in the library.
    It allows using the custom one provided by the caller.

    One of the nice things is that each tool can now print its tool name,
    e.g: "yaml2obj: error: <text>"

    Also, the code became a bit simpler.

    Differential revision: https://reviews.llvm.org/D67445 (detail/ViewSVN)
    by grimar
  4. Only initialize the streams cout/wcout/cerr/wcerr etc once, rather than any time Init::Init is called. Fixes PR#43300 (detail/ViewSVN)
    by marshall
  5. Fix build in C++20 (detail/ViewSVN)
    by ericwf

Started by an SCM change (4 times)

This run spent:

  • 1 hr 15 min waiting;
  • 1 hr 15 min build duration;
  • 2 hr 30 min total from scheduled to completion.
LLVM/Clang Warnings: 1 warning.
    Test Result (no failures)