Started 4 days 11 hr ago
Took 4 hr 44 min on green-dragon-21

Success Build #18197 (Jun 12, 2019 12:22:49 PM)

  • : 363185
  • : 363127
  • : 363167
  • : 362745
  • : 363117
  • : 363150
  1. [AMDGPU] gfx1010 premlane instructions

    Differential Revision: (detail/ViewSVN)
    by rampitec
  2. [Mips] Add s.d instruction alias for Mips1

    Add support for s.d instruction for Mips1 which expands into two swc1

    Patch by Mirko Brkusanin.

    Differential Revision: (detail/ViewSVN)
    by atanasyan
  3. [llvm-lipo] Update llvm-lipo docs for -archs flag

    The information for -archs flag is added to llvm-lipo.rst.

    Patch by Anusha Basana <>

    Differential Revision: (detail/ViewSVN)
    by smeenai
  4. [X86][SSE] Avoid unnecessary stack codegen in NT merge-consecutive-stores codegen tests. (detail/ViewSVN)
    by rksimon
  5. [SCEV] Teach computeSCEVAtScope benefit from one-input Phi. PR39673

    SCEV does not propagate arguments through one-input Phis so as to make it easy for the SCEV expander (and related code) to preserve LCSSA.  It's not entirely clear this restriction is neccessary, but for the moment it exists.   For this reason, we don't analyze single-entry phi inputs.  However it is possible that when an this input leaves the loop through LCSSA Phi, it is a provable constant.  Missing that results in an order of optimization issue in loop exit value rewriting where we miss some oppurtunities based on order in which we visit sibling loops.

    This patch teaches computeSCEVAtScope about this case. We can generalize it later, but so far we can only replace LCSSA Phis with their constant loop-exiting values.  We should probably also add similiar logic directly in the SCEV construction path itself.

    Patch by: mkazantsev (with revised commit message by me)
    Differential Revision: (detail/ViewSVN)
    by reames
  6. [TargetLowering] Add MachineMemOperand::Flags to allowsMemoryAccess tests (PR42123)

    As discussed on D62910, we need to check whether particular types of memory access are allowed, not just their alignment/address-space.

    This NFC patch adds a MachineMemOperand::Flags argument to allowsMemoryAccess and allowsMisalignedMemoryAccesses, and wires up calls to pass the relevant flags to them.

    If people are happy with this approach I can then update X86TargetLowering::allowsMisalignedMemoryAccesses to handle misaligned NT load/stores.

    Differential Revision: (detail/ViewSVN)
    by rksimon
  7. [X86][AVX] Fold concat(vpermilps(x,c),vpermilps(y,c)) -> vpermilps(concat(x,y),c)


    An extra AVX1 PSHUFD->VPERMILPS combine will be added in a future commit. (detail/ViewSVN)
    by rksimon
  8. [InstCombine] add tests for fmin/fmax libcalls; NFC (detail/ViewSVN)
    by spatel
  9. Revert rL363156.

    The patch was to fix buildbots, but rL363157 should now be fixing it
    in a cleaner way. (detail/ViewSVN)
    by sam_parker
  10. [NFC[ Updated tests for D54411 (detail/ViewSVN)
    by xbolva00
  11. gn build: Add SystemZ target (detail/ViewSVN)
    by nico
  12. StackProtector: Use PointerMayBeCaptured

    This was using its own, outdated list of possible captures. This was
    at minimum not catching cmpxchg and addrspacecast captures.

    One change is now any volatile access is treated as capturing. The
    test coverage for this pass is quite inadequate, but this required
    removing volatile in the lifetime capture test.

    Also fixes some infrastructure issues to allow running just the IR

    Fixes bug 42238. (detail/ViewSVN)
    by arsenm
  13. AMDGPU/GlobalISel: Fix using illegal situations in tests

    These were using illegal copies as the side effecting use, so make
    them legal. (detail/ViewSVN)
    by arsenm
  14. [compiler-rt] Fix test on Overlay2 (for Docker)

    This patch aims to fix the test case, that fails on Docker.

    Overlay2 on Docker does not support the current check for the name_to_handle_at()
    function call of the test case. The proposed fix is to check for /dev/null in
    the test instead, as this check is supported. Checking for /dev/null has been
    utilized in the past for other test cases, as well.

    Differential Revision: (detail/ViewSVN)
    by amyk
  15. [ARM] Fix compiler warning

    Without this fix clang 3.6 complains with:

    ../lib/Target/ARM/ARMAsmPrinter.cpp:1473:18: error: variable 'BranchTarget' is used uninitialized whenever 'if' condition is false [-Werror,-Wsometimes-uninitialized]
          } else if (MI->getOperand(1).isSymbol()) {
    ../lib/Target/ARM/ARMAsmPrinter.cpp:1479:22: note: uninitialized use occurs here
    ../lib/Target/ARM/ARMAsmPrinter.cpp:1473:14: note: remove the 'if' if its condition is always true
          } else if (MI->getOperand(1).isSymbol()) {
    ../lib/Target/ARM/ARMAsmPrinter.cpp:1465:33: note: initialize the variable 'BranchTarget' to silence this warning
          const MCExpr *BranchTarget;
                                     = nullptr
    1 error generated.

    Discussed here: (detail/ViewSVN)
    by uabelho
  16. LoopVersioning: Respect convergent

    This changes the standalone pass only. Arguably the utility class
    itself should assert there are no convergent calls. However, a target
    pass with additional context may still be able to version a loop if
    all of the dynamic conditions are sufficiently uniform. (detail/ViewSVN)
    by arsenm
  17. [MIR] Skip hoisting to basic block which may throw exception or return

    Fix hoisting to basic block which are not legal for hoisting cause
    it can be terminated by exception or it is return block.

    Reviewers: john.brawn, RKSimon, MatzeB

    Subscribers: hiraditya, llvm-commits

    Tags: #llvm

    Differential Revision: (detail/ViewSVN)
    by anton-afanasyev
  18. [InstCombine] add tests for fcmp+select with FMF (minnum/maxnum); NFC (detail/ViewSVN)
    by spatel
  19. LoopLoadElim: Respect convergent (detail/ViewSVN)
    by arsenm

Started by upstream project clang-stage2-Rthinlto_relay build number 1603
originally caused by:

This run spent:

  • 2 ms waiting;
  • 4 hr 44 min build duration;
  • 4 hr 44 min total from scheduled to completion.
Cobol Warnings: 0 warnings.
  • No warnings since build 10,378.
  • New zero warnings highscore: no warnings for 378 days!
Test Result (no failures)