Started 4 days 2 hr ago
Took 5 hr 16 min on green-dragon-02

Failed Build #14209 (Jun 12, 2019 10:33:39 PM)

  • : 363229
  • : 363220
  • : 363167
  • : 362745
  • : 363177
  • : 363219
  • : 363150
  1. [SimplifyCFG] reverting preliminary Switch patches again

    This reverts 363226 and 363227, both NFC intended

    I swear I fixed the test case that is failing, and ran
    the tests, but I will look into it again. (detail)
    by shawnl
  2. [SimpligyCFG] NFC intended, remove GCD that was only used for powers of two

    and replace with an equilivent countTrailingZeros.

    GCD is much more expensive than this, with repeated division.

    This depends on D60823

    Differential Revision: (detail)
    by shawnl
  3. [SimplifyCFG] NFC, update Switch tests to better examine successive patches

    Also add baseline tests to show effect of later patches.

    There were a couple of regressions here that were never caught,
    but my patch set that this is a preparation to will fix them.

    Differential Revision: (detail)
    by shawnl
  4. [X86] Add tests for some the special cases in EVEX to VEX to the evex-to-vex-compress.mir test. (detail)
    by ctopper
  5. [SimplifyCFG] revert the last commit.

    I ran ALL the test suite locally, so I will look into this... (detail)
    by shawnl
  6. [SimplifyCFG] NFC, update Switch tests to HEAD so I can

    see if my changes change anything

    Also add baseline tests to show effect of later patches.

    Differential Revision: (detail)
    by shawnl
  7. X86: Clean up pass initialization

    - Remove redundant initializations from pass constructors that were
      already being initialized by LLVMInitializeX86Target().

    - Add initialization function for the FPS pass.

    Reviewers: craig.topper

    Reviewed By: craig.topper

    Subscribers: hiraditya, llvm-commits

    Tags: #llvm

    Differential Revision: (detail)
    by tstellar
  8. Revert r361811: 'Re-commit r357452 (take 2): "SimplifyCFG SinkCommonCodeFromPredecessors ...'

    We have observed some failures with internal builds with this revision.

    - Performance regressions:
      - llvm's SingleSource/Misc evalloop shows performance regressions (although these may be red herrings).
      - Benchmarks for Abseil's SwissTable.
    - Correctness:
      - Failures for particular libicu tests when building the Google AppEngine SDK (for PHP).

    hwennborg has already been notified, and is aware of reproducer failures. (detail)
    by dlj
  9. Make GCC in C++03 Unsupported

    This patch make G++03 explicitly unsupported with libc++, as discussed on the mailing lists.

    Below is the rational for this decision.

    libc++ claims to support GCC with C++03 ("G++03"), and this is a problem for our users.

    Our C++03 users are all using Clang. They must be.  Less than 9% of the C++03 tests pass with GCC [1][2]. No non-trivial C++ program could work.

    Attempting to support G++03 impacts our QoI considerably. Unlike Clang, G++03 offers almost no C++11 extensions. If we could remove all the fallbacks for G++03, it would mean libc++ could::

    * Improve Correctness:

    Every `#ifdef _LIBCPP_HAS_NO_<C++11-feature>` is a bug manifest. It exists to admit for deviant semantics.

    * Achieve ABI stability between C++03 and C++11

    Differences between our C++03 and C++Rest branches contain ABI bugs. For example `std::nullptr_t` and `std::function::operator()(...)` are currently incompatible between C++11 and C++03, but could be fixed.

    * Decrease Compile Times and Memory Usage:

    Writing efficient SFINAE requires C++11. Using alias templates, libc++ could reduce the number of instantiations it produces substantially.

    * Decrease Binary Size

    Similar to the last point, G++03 forces metaprogramming techniques that emit more debug information [3] [4]. Compared to libstdc++, debug information size increases of +10% are not uncommon.

    Reviewers: ldionne, mclow.lists, EricWF

    Reviewed By: ldionne, EricWF

    Subscribers: zoecarver, aprantl, dexonsmith, arphaman, libcxx-commits, #libc

    Differential Revision: (detail)
    by ericwf

Started by timer (5 times)

This run spent:

  • 4 hr 22 min waiting;
  • 5 hr 16 min build duration;
  • 9 hr 39 min total from scheduled to completion.

Identified problems

No identified problem

No problems were identified. If you know why this problem occurred, please add a suitable Cause for it.