Started 2 yr 5 mo ago
Took 3 min 27 sec on green-dragon-15

Failed Build #289 (Feb 12, 2019 6:49:06 AM)

  • : 353842
  • : 353840
  • : 353820
  • : 346271
  • : 353786
  • : 353821
  1. [LoopSimplifyCFG] Fix test broken in release mode in r353813 (detail/ViewSVN)
    by sammccall
  2. [Sema] Fix a crash in access checking for deduction guides

    Summary: See the added test for a repro.

    Reviewers: sammccall

    Reviewed By: sammccall

    Subscribers: cfe-commits

    Tags: #clang

    Differential Revision: (detail/ViewSVN)
    by ibiryukov
  3. Renaming yet another diagnostic to not conflict; NFC. (detail/ViewSVN)
    by aaronballman
  4. Renaming this diagnostic to not conflict with another; NFC.

    Amends r353837 which renamed the diagnostics to conflict. (detail/ViewSVN)
    by aaronballman
  5. Fixing a typo; NFC. (detail/ViewSVN)
    by aaronballman
  6. Disable test after r353718, r353725, r353729 while I investigate (detail/ViewSVN)
    by nico
  7. [NFC] Simplify code & reduce nest slightly (detail/ViewSVN)
    by mkazantsev
  8. [DebugInfo] Don't salvage load operations (PR40628).

    Salvaging a redundant load instruction into a debug expression hides a
    memory read from optimisation passes. Passes that alter memory behaviour
    (such as LICM promoting memory to a register) aren't aware of these debug
    memory reads and leave them unaltered, making the debug variable location
    point somewhere unsafe.

    Teaching passes to know about these debug memory reads would be challenging
    and probably incomplete. Finding dbg.value instructions that need to be fixed
    would likely be computationally expensive too, as more analysis would be
    required. It's better to not generate debug-memory-reads instead, alas.

    Changed tests:
    * DeadStoreElim: test for salvaging of intermediate operations contributing
       to the dead store, instead of salvaging of the redundant load,
    * GVN: remove debuginfo behaviour checks completely, this behaviour is still
       covered by other tests,
    * InstCombine: don't test for salvaged loads, we're removing that behaviour.

    Differential Revision: (detail/ViewSVN)
    by jmorse
  9. [DebugInfo] Keep parameter DBG_VALUEs before prologue code

    This is a preparatory change for removing the code from
    DebugHandlerBase::beginFunction() which changes the starting label for
    the first non-overlapping DBG_VALUEs of parameters to the beginning of
    the function. It does that to be able to show parameters when entering a
    function. However, that code does not consider what defines the values,
    which can result in the ranges for the debug values starting before
    their defining instructions. That code is removed in a follow-up patch.

    When prologue code is inserted, it leads to DBG_VALUEs that start
    directly in the entry block being moved down after the prologue
    instructions. This patch fixes that by stashing away DBG_VALUEs for
    parameters before emitting the prologue, and then reinserts them at the
    start of the block. This assumes that there is no target that somehow
    clobbers parameter registers in the frame setup; there is no such case
    in the lit tests at least.

    See PR40188 for more information.

    Reviewers: aprantl, dblaikie, rnk, jmorse

    Reviewed By: aprantl

    Subscribers: bjope, llvm-commits

    Tags: #debug-info

    Differential Revision: (detail/ViewSVN)
    by dstenb
  10. [clangd] Fix use-after-free in XRefs (detail/ViewSVN)
    by sammccall
  11. tsan: update

    Update numbers after 353817.
    This was extensively benchmarked in (detail/ViewSVN)
    by dvyukov
  12. tsan: add fiber support

    This patch adds functions for managing fibers:


    See the added tests for use examples.

    Author: yuri (Yuri Per)
    Reviewed in: (detail/ViewSVN)
    by dvyukov
  13. [IndVars] Fix corner case with unreachable Phi inputs. PR40454

    Logic in `getInsertPointForUses` doesn't account for a corner case when `Def`
    only comes to a Phi user from unreachable blocks. In this case, the incoming
    value may be arbitrary (and not even available in the input block) and break
    the loop-related invariants that are asserted below.

    In fact, if we encounter this situation, no IR modification is needed. This
    Phi will be simplified away with nearest cleanup.

    Differential Revision:
    Reviewed By: spatel (detail/ViewSVN)
    by mkazantsev
  14. [llvm-readobj] Only allow 4-byte pr_data

    Summary: AMD64 psABI says: "The pr_data field of each property contains a 4-byte unsigned integer." Thus we don't need to handle 8-byte pr_data.

    Reviewers: mike.dvoretsky, grimar, craig.topper, xiangzhangllvm,

    Reviewed By: grimar

    Subscribers: rupprecht, llvm-commits

    Tags: #llvm

    Differential Revision: (detail/ViewSVN)
    by maskray
  15. [llvm-readobj] - Simplify .gnu.version_r dumping a bit.

    Current implementation takes "Number of needed versions" from DT_VERNEEDNUM
    dynamic tag entry. Though it would be a bit simpler to take it from sh_info
    section header field directly:

    Differential revision: (detail/ViewSVN)
    by grimar
  16. [LoopSimplifyCFG] Change logic of dead loops removal to avoid hitting asserts

    The function `LI.erase` has some invariants that need to be preserved when it
    tries to remove a loop which is not the top-level loop. In particular, it
    requires loop's preheader to be strictly in loop's parent. Our current logic
    of deletion of dead blocks may erase the information about preheader before we
    handle the loop, and therefore we may hit this assertion.

    This patch changes the logic of loop deletion: we make them top-level loops
    before we actually erase them. This allows us to trigger the simple branch of
    `erase` logic which just detatches blocks from the loop and does not try to do
    some complex stuff that need this invariant.

    Thanks to @uabelho for reporting this!

    Differential Revision:
    Reviewed By: fedor.sergeev (detail/ViewSVN)
    by mkazantsev
  17. [yaml2obj/obj2yaml] - Move `Info` field out from `Section` class.

    ELFYAML.h contains a `Section` class which is a base for a few other
    sections classes that are used for mapping different section types.
    `Section` has a `StringRef Info` field used for storing sh_info.

    At the same time, sh_info has very different meanings for sections and
    cannot be processed in a similar way generally,
    for example ELFDumper does not handle it in `dumpCommonSection`
    but do that in `dumpGroup` and `dumpCommonRelocationSection` respectively.

    At this moment, we have and handle it as a string, because that was possible for
    the current use case. But also it can simply be a number:
    For SHT_GNU_verdef is "The number of version definitions within the section."

    The patch moves `Info` field out to be able to have it as a number.
    With that change, each class will be able to decide what type and purpose
    of the sh_info field it wants to use.

    I also had to edit 2 test cases. This is because patch fixes a bug. Previously we
    accepted yaml files with Info fields for all sections (for example, for SHT_DYNSYM too).
    But we do not handle it and the resulting objects had zero sh_info fields set for
    such sections. Now it is accepted only for sections that supports it.

    Differential revision: (detail/ViewSVN)
    by grimar
  18. LibFuzzer.rst: double backticks (detail/ViewSVN)
    by hans
  19. tsan: Introduce in_symbolizer() function for Thread sanitizer

    This change is preparation for fiber support.

    Author: yuri (Yuri Per)
    Reviewed in: (detail/ViewSVN)
    by dvyukov
  20. Delete blocks from DTU to avoid dangling pointers (detail/ViewSVN)
    by mkazantsev
  21. [LoopSimplifyCFG] Pay respect to LCSSA when removing dead blocks

    Utility function that we use for blocks deletion always unconditionally removes
    one-input Phis. In LoopSimplifyCFG, it can lead to breach of LCSSA form.
    This patch alters this function to keep them if needed.

    Differential Revision:
    Reviewed By: fedor.sergeev (detail/ViewSVN)
    by mkazantsev
  22. [X86] Use the new unaligned vector typedefs for the loadu/storeu intrinsics pointer arguments.

    This matches what gcc does and what was suggested by rnk in PR20670. (detail/ViewSVN)
    by ctopper
  23. [NFC] Rename DontDeleteUselessPHIs --> KeepOneInputPHIs (detail/ViewSVN)
    by mkazantsev
  24. [Statepoint Lowering] Update misleading comments about chains (detail/ViewSVN)
    by reames
  25. [NFC] Add parameter for keeping one-input Phis in DeleteDeadBlock(s) (detail/ViewSVN)
    by mkazantsev
  26. [X86] Collapse FP_TO_INT16_IN_MEM/FP_TO_INT32_IN_MEM/FP_TO_INT64_IN_MEM into a single opcode using memory VT to distinquish. NFC (detail/ViewSVN)
    by ctopper
  27. [X86] Remove the value type operand from the floating point load/store MemIntrinsicSDNodes. Use the MemoryVT instead. NFCI

    We already have the memory VT, we can just match from that during isel. (detail/ViewSVN)
    by ctopper

Started by upstream project Clang Stage 2: cmake, R -g Asan&UBSan, using Stage 1 RA, Phase 1 build number 6129
originally caused by:

This run spent:

  • 5.4 sec waiting;
  • 3 min 27 sec build duration;
  • 3 min 32 sec total from scheduled to completion.

Identified problems

Missing test results

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

CMake Error

This build failed because of an CMake configuration error. Below is a list of all errors in the build log:
Indication 2