Started 2 hr 18 min ago
Build has been executing for 2 hr 18 min on green-dragon-02

Progress:
In progress Build #14908 (Oct 18, 2019 3:15:16 PM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 375293
  • http://llvm.org/svn/llvm-project/cfe/trunk : 375286
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 375284
  • http://llvm.org/svn/llvm-project/zorg/trunk : 375291
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 374854
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 375226
Changes
  1. [AMDGPU] Remove -amdgpu-spill-sgpr-to-smem.

    Summary: The implementation was never completed and never used except in tests.

    Reviewers: arsenm, mareko

    Subscribers: qcolombet, kzhuravl, jvesely, wdng, nhaehnle, yaxunl, dstuttard, tpr, t-tye, hiraditya, llvm-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D69163 (detail)
    by foad
  2. [sanitizers] Increase default "git clone --depth" to 100 (detail)
    by Vitaly Buka
  3. [CVP] setDeducedOverflowingFlags(): actually inc per-opcode stats

    This is really embarrassing. Those are pointers, so that offsets the
    pointers, not the statistics pointed-by the pointer... (detail)
    by lebedevri
  4. gn build: Merge r375288 (detail)
    by gnsyncbot
  5. Disable exit-on-SIGPIPE in lldb

    Occasionally, during test teardown, LLDB writes to a closed pipe.
    Sometimes the communication is inherently unreliable, so LLDB tries to
    avoid being killed due to SIGPIPE (it calls `signal(SIGPIPE, SIG_IGN)`).
    However, LLVM's default SIGPIPE behavior overrides LLDB's, causing it to
    exit with IO_ERR.

    Opt LLDB out of the default SIGPIPE behavior. I expect that this will
    resolve some LLDB test suite flakiness (tests randomly failing with
    IO_ERR) that we've seen since r344372.

    rdar://55750240

    Differential Revision: https://reviews.llvm.org/D69148 (detail)
    by Vedant Kumar
  6. [X86] Fix register parsing in .seh_* in Intel syntax

    Previously, the parser checked for a '%' prefix to indicate a register.
    In Intel syntax mode, LLVM does not print a '%' prefix on registers, so
    LLVM could not parse its own assembly output. Instead, require that
    register numbers be integer literals, or at least start with an integer
    literal, which is consistent with .cfi_* directive register parsing. (detail)
    by rnk
  7. [analyzer] exploded-graph-rewriter: Unforget to censor stmt_ids in the test.

    They're not stable across machines.

    Fixes buildbots after r375278. (detail)
    by dergachev
  8. [NFC][CVP] Some tests for `mul` no-wrap deduction (detail)
    by lebedevri
  9. Update global_symbols.txt. (detail)
    by pcc
  10. [WebAssembly] Allow multivalue signatures in object files

    Summary:
    Also changes the wasm YAML format to reflect the possibility of having
    multiple return types and to put the returns after the params for
    consistency with the binary encoding.

    Reviewers: aheejin, sbc100

    Subscribers: dschuff, jgravelle-google, hiraditya, sunfish, arphaman, rupprecht, llvm-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D69156 (detail)
    by tlively
  11. [analyzer] exploded-graph-rewriter: Rename Environment to Expressions.

    It's less confusing for newcomers. (detail)
    by dergachev
  12. [analyzer] Fix FieldRegion dumps.

    The '->' thing has always been confusing; the actual operation '->'
    translates to a pointer dereference together with adding a FieldRegion,
    but FieldRegion on its own doesn't imply an additional pointer
    dereference. (detail)
    by dergachev
  13. [analyzer] Drop the logic for collapsing the state if it's same as in preds.

    One of the first attempts to reduce the size of the exploded graph dumps
    was to skip the state dump as long as the state is the same as in all of
    the predecessor nodes. With all the new facilities in place (node joining,
    diff dumps), this feature doesn't do much, and when it does,
    it's more harmful than useful. Let's remove it. (detail)
    by dergachev
  14. [analyzer] exploded-graph-rewriter: Fix dump for state 0.

    It shouldn't say "unspecified" when the state is specified to be empty. (detail)
    by dergachev
  15. [analyzer] Fix hidden node traversal in exploded graph dumps.

    The joined nodes now actually have the same state. That was intended
    from the start but the original implementation turned out to be buggy.

    Differential Revision: https://reviews.llvm.org/D69150 (detail)
    by dergachev
  16. [GISel][CallLowering] Make isIncomingArgumentHandler a pure virtual method

    The default implementation of isIncomingArgumentHandler could lead
    to generating incorrect code.
    Make it a pure virtual method, so that targets know they have to
    override it to produce correct code.

    NFC

    Differential Revision: https://reviews.llvm.org/D69187 (detail)
    by qcolombet
  17. scudo: Update TLS_SLOT_SANITIZER value.

    Android now allocates only 8 fixed TLS slots. Somehow we were getting away
    with using a non-existent slot until now, but in some cases the TLS slots
    were being placed at the end of a page, which led to a segfault at startup.

    Differential Revision: https://reviews.llvm.org/D69191 (detail)
    by pcc
  18. [CVP] After proving that @llvm.with.overflow()/@llvm.sat() don't overflow, also try to prove other no-wrap

    Summary:
    CVP, unlike InstCombine, does not run till exaustion.
    It only does a single pass.

    When dealing with those special binops, if we prove that they can
    safely be demoted into their usual binop form,
    we do set the no-wrap we deduced. But when dealing with usual binops,
    we try to deduce both no-wraps.

    So if we convert e.g. @llvm.uadd.with.overflow() to `add nuw`,
    we won't attempt to check whether it can be `add nuw nsw`.

    This patch proposes to call `processBinOp()` on newly-created binop,
    which is identical to what we do for div/rem already.

    Reviewers: nikic, spatel, reames

    Reviewed By: nikic

    Subscribers: hiraditya, llvm-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D69183 (detail)
    by lebedevri
  19. [examples] Fix some comments in the LLJITWithJITLink example (detail)
    by Lang Hames
  20. Apply defaut cmake flags to ABITestsuitBuilder. (detail)
    by gkistanova
  21. AMDGPU: Relax 32-bit SGPR register class

    Mostly use SReg_32 instead of SReg_32_XM0 for arbitrary values. This
    will allow the register coalescer to do a better job eliminating
    copies to m0.

    For GlobalISel, as a terrible hack, use SGPR_32 for things that should
    use SCC until booleans are solved. (detail)
    by arsenm
  22. [examples] Add an example of how to use JITLink and small-code-model with LLJIT.

    JITLink is LLVM's newer jit-linker. It is an alternative to (and hopefully
    eventually a replacement for) LLVM's older jit-linker, RuntimeDyld. Unlike
    RuntimeDyld which requries JIT'd code to be complied with the large code
    model, JITlink can link code compiled with the small code model, which is
    the native code model for a number of targets (including all supported MachO
    targets).

    This example shows how to:

    -- Create a JITLink InProcessMemoryManager
    -- Set the code model to small
    -- Use a JITLink backed ObjectLinkingLayer as the linking layer for LLJIT
       (rather than the default RTDyldObjectLinkingLayer).

    Note: This example will only work on platforms supported by JITLink. As of
    this commit that's MachO/x86-64 and MachO/arm64. (detail)
    by Lang Hames
  23. AMDGPU: Fix SMEM WAR hazard for gfx10 readlane

    Summary: Hazard recognizer fails to see hazard with V_READLANE_B32_gfx10.

    Reviewers: rampitec

    Reviewed By: rampitec

    Subscribers: arsenm, kzhuravl, jvesely, wdng, nhaehnle, yaxunl, dstuttard, tpr, t-tye, hiraditya, llvm-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D69172 (detail)
    by kerbowa
  24. [lit] Reduce value of synthesized timeouts

    Large timeout values (one year, positive infinity) trip up Python on
    Windows with "OverflowError: timeout value is too large".  One week
    seems to work and is still large enough in practice.

    Thanks to Simon Pilgrim for helping me test this.
    https://reviews.llvm.org/rL375171 (detail)
    by yln

Started by timer (5 times)

This run spent 4 hr 4 min waiting in the queue.