Started 6 days 21 hr ago
Took 4 hr 54 min on green-dragon-02

Failed Build #14199 (Jun 10, 2019 2:57:42 AM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 362925
  • http://llvm.org/svn/llvm-project/cfe/trunk : 362924
  • 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 : 362866
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 362811
Changes
  1. [yaml2obj] - Remove helper methods that are probably excessive. NFC.

    These methods are used only once. One of them is not used at all.

    Differential revision: https://reviews.llvm.org/D63002 (detail)
    by grimar
  2. Revert "Revert "[CodeComplete] Improve overload handling for C++ qualified and ref-qualified methods.""

    This reverts commit r362830, and relands r362785 with the leak fixed. (detail)
    by sammccall
  3. [DebugInfo] More strict debug range for stack variables

    Variable's stack location can stretch longer than it should. If a
    variable is placed at the stack in a some nested basic block its range
    can be calculated to be up to the next occurrence of the variable's
    DBG_VALUE, or up to the end of the function, thus covering a basic
    blocks that should not be included in the variable’s location range.
    This happens because the DbgEntityHistoryCalculator ends register
    locations at the end of a basic block only if the variable’s location
    register has been changed throughout the function, which is not the
    case for the register used to reference stack objects.

    This patch also tries to produce a single value location if the location
    list builder managed to merge all the locations into one.

    Reviewers: aprantl, dstenb, jmorse

    Reviewed By: aprantl, dstenb, jmorse

    Subscribers: djtodoro, ivanbaev, asowda

    Tags: #debug-info

    Differential Revision: https://reviews.llvm.org/D61600 (detail)
    by nikolaprica
  4. [DAGCombine] Match a pattern where a wide type scalar value is stored by several narrow stores
    This opportunity is found from spec 2017 557.xz_r. And it is used by the sha encrypt/decrypt. See sha-2/sha512.c

    static void store64(u64 x, unsigned char* y)
    {
        for(int i = 0; i != 8; ++i)
            y[i] = (x >> ((7-i) * 8)) & 255;
    }

    static u64 load64(const unsigned char* y)
    {
        u64 res = 0;
        for(int i = 0; i != 8; ++i)
            res |= (u64)(y[i]) << ((7-i) * 8);
        return res;
    }
    The load64 has been implemented by https://reviews.llvm.org/D26149
    This patch is trying to implement the store pattern.

    Match a pattern where a wide type scalar value is stored by several narrow
    stores. Fold it into a single store or a BSWAP and a store if the targets
    supports it.

    Assuming little endian target:
    i8 *p = ...
    i32 val = ...
    p[0] = (val >> 0) & 0xFF;
    p[1] = (val >> 8) & 0xFF;
    p[2] = (val >> 16) & 0xFF;
    p[3] = (val >> 24) & 0xFF;

    >
    *((i32)p) = val;

    i8 *p = ...
    i32 val = ...
    p[0] = (val >> 24) & 0xFF;
    p[1] = (val >> 16) & 0xFF;
    p[2] = (val >> 8) & 0xFF;
    p[3] = (val >> 0) & 0xFF;

    >
    *((i32)p) = BSWAP(val);

    Differential Revision: https://reviews.llvm.org/D62897 (detail)
    by qshanz

Started by timer (5 times)

This run spent:

  • 4 hr 46 min waiting;
  • 4 hr 54 min build duration;
  • 9 hr 41 min total from scheduled to completion.

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

Missing test results

The test result file Jenkins is looking for does not exist after the build.
Indication 2

Ninja target failed

Below is a link to the first failed ninja target.
Indication 3

Regression test failed

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