Started 11 days ago
Took 5 hr 13 min on green-dragon-02

Failed Build #14668 (Sep 10, 2019 4:50:48 PM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 371573
  • http://llvm.org/svn/llvm-project/cfe/trunk : 371571
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 371574
  • http://llvm.org/svn/llvm-project/zorg/trunk : 371154
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 371324
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 371504
Changes
  1. Remove xfail NetBSD mark from ignored-interceptors-mmap.cpp

    This test now passes. (detail)
    by kamil
  2. [MemorySSA] MemorySSA should not model debuginfo, and need not update it.

    Reverts the change in r371084, but keeps the test.
    After r371565, debuginfo cannot be modelled in MemorySSA, even with a
    non-standard AA pipeline. (detail)
    by asbirlea
  3. [GlobalISel] When a tail call is emitted in a block, stop translating it

    This fixes a crash in tail call translation caused by assume and lifetime_end
    intrinsics.

    It's possible to have instructions other than a return after a tail call which
    will still have `Analysis::isInTailCallPosition` return true. (Namely,
    lifetime_end and assume intrinsics.)

    If we emit a tail call, we should stop translating instructions in the block.
    Otherwise, we can end up emitting an extra return, or dead instructions in
    general. This makes the verifier unhappy, and is generally unfortunate for
    codegen.

    This also removes the code from AArch64CallLowering that checks if we have a
    tail call when lowering a return. This is covered by the new code now.

    Also update call-translator-tail-call.ll to show that we now properly tail call
    in the presence of lifetime_end and assume.

    Differential Revision: https://reviews.llvm.org/D67415 (detail)
    by paquette
  4. [clang-format] Apply BAS_AlwaysBreak to C++11 braced lists

    See PR18455.

    Differential Revision: https://reviews.llvm.org/D67395 (detail)
    by owenpan
  5. [AArch64][GlobalISel] Support sibling calls with mismatched calling conventions

    Add support for sibcalling calls whose calling convention differs from the
    caller's.

    - Port over `CCState::resultsCombatible` from CallingConvLower.cpp into
      CallLowering. This is used to verify that the way the caller and callee CC
      handle incoming arguments matches up.

    - Add `CallLowering::analyzeCallResult`. This is basically a port of
      `CCState::AnalyzeCallResult`, but using `ArgInfo` rather than `ISD::InputArg`.

    - Add `AArch64CallLowering::doCallerAndCalleePassArgsTheSameWay`. This checks
      that the calling conventions are compatible, and that the caller and callee
      preserve the same registers.

    For testing:

    - Update call-translator-tail-call.ll to show that we can now handle this.

    - Add a GISel line to tailcall-ccmismatch.ll to show that we will not tail call
      when the regmasks don't line up.

    Differential Revision: https://reviews.llvm.org/D67361 (detail)
    by paquette
  6. Update ReleaseNotes: add enabling of MemorySSA. (detail)
    by asbirlea
  7. Reland "Change the X86 datalayout to add three address spaces
    for 32 bit signed, 32 bit unsigned, and 64 bit pointers."
    This reverts 57076d3199fc2b0af4a3736b7749dd5462cacda5.

    Original review at https://reviews.llvm.org/D64931.
    Review for added fix at https://reviews.llvm.org/D66843. (detail)
    by akhuang
  8. llvm-reduce: Add pass to reduce parameters

    Patch by Diego Treviño!

    Differential Revision: https://reviews.llvm.org/D65479 (detail)
    by dblaikie
  9. Adding support for overriding LLVM_ENABLE_RUNTIMES for runtimes builds.

    On some platforms, certain runtimes are not supported. For runtimes builds of
    those platforms it would be nice if we could disable certain runtimes (ie
    libunwind on Windows).



    Differential Revision: https://reviews.llvm.org/D67195 (detail)
    by zer0
  10. [MemorySSA] Do not create memoryaccesses for debug info intrinsics.

    Summary:
    Do not model debuginfo intrinsics in MemorySSA.
    Regularly these are non-memory modifying instructions. With -disable-basicaa, they were being modelled as Defs.

    Reviewers: george.burgess.iv

    Subscribers: aprantl, Prazek, sanjoy.google, llvm-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D67307 (detail)
    by asbirlea
  11. llvm-reduce: Remove some unused headers/more narrowly include them (detail)
    by dblaikie
  12. llvm-remove: Remove "using namespace" in header. (detail)
    by dblaikie
  13. llvm-reduce: Add pass to reduce Metadata

    Patch by Diego Treviño!

    Differential Revision: https://reviews.llvm.org/D65026 (detail)
    by dblaikie
  14. Move LLVM_ENABLE_ABI_BREAKING_CHECKS variables to their own file
    so that you don't have to link Error.o and all of its dependencies.

    In more detail: global initializers in Error.o can't be elided with
    -ffunction-sections/-gc-sections since they always need to be run
    causing a fairly significant binary bloat if all you want is the
    ABI breaking checks code.

    Differential Revision: https://reviews.llvm.org/D67387 (detail)
    by echristo
  15. Actually reorder not and env in crash-recovery-modules.m (detail)
    by rnk
  16. [Loads] Move generic code out of vectorizer into a location it might be reused [NFC] (detail)
    by reames
  17. When evaluating a __builtin_constant_p conditional, always enter
    constant-folding mode regardless of the original evaluation mode.

    In order for this to be correct, we need to track whether we're checking
    for a potential constant expression or checking for undefined behavior
    separately from the evaluation mode enum, since we don't want to clobber
    those states when entering constant-folding mode. (detail)
    by rsmith
  18. [ValueTracking] Factor our common speculation suppression logic [NFC]

    Expose a utility function so that all places which want to suppress speculation (when otherwise legal) due to ordering and/or sanitizer interaction can do so. (detail)
    by reames
  19. llvm-reduce: Simplify testing using -implicit-check-not

    Also fix llvm-reduce to use the specified output file name directly,
    without appending '.ll' to the name. (detail)
    by dblaikie
  20. [OPENMP5.0]Allow teams directive outside of the target directives.

    According to OpenMP 5.0, teams directives are allowed not only in the
    target context, but also in the implicit parallel regions. (detail)
    by abataev
  21. Re-land Remove REQUIRES:shell from tests that pass for me on Windows

    This reverts r371497 (git commit 3d7e9ab7b9f8c53aa41420c54970f0fb421004a2)

    Reorder `not` with `env` in these two tests so they pass:
      Driver/rewrite-map-in-diagnostics.c
      Index/crash-recovery-modules.m.

    This will not be necessary after D66531 lands. (detail)
    by rnk
  22. [x86] add test for false dependency with AVX; NFC

    Goes with D67363 (detail)
    by spatel
  23. [NFC][InstCombine] rewrite test added in r371537 to use non-null pointer instead

    I only want to ensure that %offset is non-zero there,
    it doesn't matter how that info is conveyed.
    As filed in PR43267, the assumption way does not work. (detail)
    by lebedevri
  24. Fix for PR43175: compiler crash when trying to emit noncapturable
    constant.

    If the constexpr variable is partially initialized, the initializer can
    be emitted as the structure, not as an array, because of some early
    optimizations. The llvm variable gets the type from this constant and,
    thus, gets the type which is pointer to struct rather than pointer to an
    array. We need to convert this type to be truely array, otherwise it may
    lead to the compiler crash when trying to emit array subscript
    expression. (detail)
    by abataev
  25. [X86] Updated target specific selection dag code to conservatively check for isAtomic in addition to isVolatile

    See D66309 for context.

    This is the first sweep of x86 target specific code to add isAtomic bailouts where appropriate. The intention here is to have the switch from AtomicSDNode to LoadSDNode/StoreSDNode be close to NFC; that is, I'm not looking to allow additional optimizations at this time.

    Sorry for the lack of tests.  As discussed in the review, most of these are vector tests (for which atomicity is not well defined) and I couldn't figure out to exercise the anyextend cases which aren't vector specific.

    Differential Revision: https://reviews.llvm.org/D66322 (detail)
    by reames
  26. [NFC][InstSimplify] rewrite test added in r371537 to use non-null pointer instead

    I only want to ensure that %offset is non-zero there,
    it doesn't matter how that info is conveyed.
    As filed in PR43267, the assumption way does not work. (detail)
    by lebedevri

Started by timer (5 times)

This run spent:

  • 4 hr 40 min waiting;
  • 5 hr 13 min build duration;
  • 9 hr 53 min total from scheduled to completion.
Test Result (4 failures / +2)Show all failed tests >>>

Identified problems

Regression test failed

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

Compile Error

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

Assertion failure

This build failed because of an assertion failure. Below is a list of all errors in the build log:
Indication 3

Ninja target failed

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