Started 1 yr 8 mo ago
Took 56 min

Failed Build clang-r359557-t56014-b56014.tar.gz (Apr 30, 2019 6:56:59 AM)


Found 1 issues:
Error: <html>
+ . /Users/buildslave/jenkins/workspace/lnt-test-suite-x86_64-O3-flto/config/tasks/utils/
++ echo '@@@ LNT Submit @@@'
@@@ LNT Submit @@@
++ '[' -n -a -n lnt-test-suite-x86_64-O3-flto ']'
+++ lnt submit /Users/buildslave/jenkins/workspace/lnt-test-suite-x86_64-O3-flto/lnt-sandbox/report.json
++ LNT_RESULT_URL='error: <html>

<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">

Build Log

Revision: 358206
  1. vs integration: vs2019 support (detail)
    by hans
  2. [cmake] Fix error message on simulated VS version check

    For clang-cl self hosts in VS2015 environment this was reporting: "Host
    Clang must have at least -fms-compatibility-version=19.00.24213.1, your
    version is 9.0.0".

    This check fires as CMake detects the simulated environment as _MSC_VER
    1900, which is truncated. This makes it less than the required

    Differential revision: (detail)
    by russell_gallop
  3. Revert rL359519 : [MemorySSA] Invalidate MemorySSA if AA or DT are invalidated.

    MemorySSA keeps internal pointers of AA and DT.
    If these get invalidated, so should MemorySSA.

    Reviewers: george.burgess.iv, chandlerc

    Subscribers: jlebar, Prazek, llvm-commits

    Tags: #llvm

    Differential Revision:
    This was causing windows build bot failures (detail)
    by rksimon
  4. [SLP] Lit test that cannot get vectorized due to lack of look-ahead operand reordering heuristic.

    The code in this test is not vectorized by SLP because its operand reordering cannot look beyond the immediate predecessors.
    This will get fixed in a follow-up patch that introduces the look-ahead operand reordering heuristic.

    Committed on behalf of @vporpo (Vasileios Porpodas)

    Differential Revision: (detail)
    by rksimon
  5. [llvm-objcopy] - Check dynamic relocation sections for broken references.

    This is a fix for

    Currently, it is possible to break the sh_link field of the dynamic relocation section
    by removing the section it refers to. The patch fixes an issue and adds 2 test cases.

    One of them shows that it does not seem possible to break the sh_info field.
    I added an assert to verify this.

    Differential revision: (detail)
    by grimar
  6. Update checks in an instcombine test, NFC

    This reduces the delta in some incoming work that changes this test. (detail)
    by jmorse
  7. [ARM] Implement TTI::getMemcpyCost

    This implements TargetTransformInfo method getMemcpyCost, which estimates the
    number of instructions to which a memcpy instruction expands to.

    Differential Revision: (detail)
    by sjoerdmeijer
  8. Fix for bug 41512: lower INSERT_VECTOR_ELT(ZeroVec, 0, Elt) to SCALAR_TO_VECTOR(Elt) for all SSE flavors

    Current LLVM uses pxor+pinsrb on SSE4+ for INSERT_VECTOR_ELT(ZeroVec, 0, Elt) insead of much simpler movd.
    INSERT_VECTOR_ELT(ZeroVec, 0, Elt) is idiomatic construct which is used e.g. for _mm_cvtsi32_si128(Elt) and for lowest element initialization in _mm_set_epi32.
    So such inefficient lowering leads to significant performance digradations in ceratin cases switching from SSSE3 to SSE4.

    Here INSERT_VECTOR_ELT(ZeroVec, 0, Elt) is simply converted to SCALAR_TO_VECTOR(Elt) when applicable since latter is closer match to desired behavior and always efficiently lowered to movd and alike.

    Committed on behalf of @Serge_Preis (Serge Preis)

    Differential Revision: (detail)
    by rksimon
Revision: 358206
  1. Fix gcc "-Wdangling-else" warning. NFCI. (detail)
    by rksimon
  2. Fix gcc "-Wdangling-else" warnings. NFCI. (detail)
    by rksimon
Revision: 358206
  1. Fix Wpedantic "default argument specified for lambda parameter" warning. NFCI. (detail)
    by rksimon

Started by upstream project relay-lnt-test-suite build number 7135
originally caused by:

This run spent:

  • 13 min waiting;
  • 56 min build duration;
  • 56 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.