Started 4 days 2 hr ago
Took 3 hr 29 min on green-dragon-19

Failed Build rL:363423 - C:363430 - #57497 (Jun 14, 2019 10:17:10 AM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 363423
  • http://llvm.org/svn/llvm-project/cfe/trunk : 363430
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 363358
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 362745
  • http://llvm.org/svn/llvm-project/zorg/trunk : 363366
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 363405
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 363375
Changes
  1. Remove unused SK_LValueToRValue initialization step.

    In addition to being unused and duplicating code, this was also wrong
    (it didn't properly mark the operand as being potentially not odr-used).

    This reinstates r363340, reverted in r363352. (detail/ViewSVN)
    by rsmith
  2. PR23833, DR2140: an lvalue-to-rvalue conversion on a glvalue of type
    nullptr_t does not access memory.

    We now reuse CK_NullToPointer to represent a conversion from a glvalue
    of type nullptr_t to a prvalue of nullptr_t where necessary.

    This reinstates r363337, reverted in r363352. (detail/ViewSVN)
    by rsmith
  3. C++ DR712 and others: handle non-odr-use resulting from an lvalue-to-rvalue conversion applied to a member access or similar not-quite-trivial lvalue expression.

    Summary:
    When a variable is named in a context where we can't directly emit a
    reference to it (because we don't know for sure that it's going to be
    defined, or it's from an enclosing function and not captured, or the
    reference might not "work" for some reason), we emit a copy of the
    variable as a global and use that for the known-to-be-read-only access.

    This reinstates r363295, reverted in r363352, with a fix for PR42276:
    we now produce a proper name for a non-odr-use reference to a static
    constexpr data member. The name <mangled-name>.const is used in that
    case; such names are reserved to the implementation for cases such as
    this and should demangle nicely.

    Reviewers: rjmccall

    Subscribers: jdoerfert, cfe-commits

    Tags: #clang

    Differential Revision: https://reviews.llvm.org/D63157 (detail/ViewSVN)
    by rsmith
  4. [PowerPC][NFC] Format comments in P9InstrResrouce.td (detail/ViewSVN)
    by jsji
  5. [SimpligyCFG] NFC intended, remove GCD that was only used for powers of two

    and replace with an equilivent countTrailingZeros.

    GCD is much more expensive than this, with repeated division.

    This depends on D60823

    Differential Revision: https://reviews.llvm.org/D61151 (detail/ViewSVN)
    by shawnl
  6. build: don't attempt to run config.guess on Windows

    When cross-compiling LLVM to android from Windows (for LLVMSupport), we would
    attempt to execute `config.guess` to determine the host triple since
    `CMAKE_SYSTEM_NAME` is not Windows and `CMAKE_C_COMPILER` will be set to GNU or
    Clang.  This will fail as `config.guess` is a shell script which cannot be
    executed on Windows.  Simply log a warning instead.  The user can specify the
    value for this instead in those cases. (detail/ViewSVN)
    by Saleem Abdulrasool
  7. [AMDGPU] Don't constrain callees with inlinehint from inlining on MaxBB check

    Summary: Function bodies marked inline in an opencl source are eliminated but MaxBB check may prevent inlining them leaving undefined references.

    Reviewers: rampitec, arsenm

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

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D63337 (detail/ViewSVN)
    by vpykhtin
  8. [FPEnv] Lower STRICT_FP_EXTEND and STRICT_FP_ROUND nodes in preprocess phase of ISelLowering to mirror non-strict nodes on x86.

    I recently discovered a bug on the x86 platform: The fp80 type was not handled well by x86 for constrained floating point nodes, as their regular counterparts are replaced by extending loads and truncating stores during the preprocess phase. Normally, platforms don't have this issue, as they don't typically attempt to perform such legalizations during instruction selection preprocessing. Before this change, strict_fp nodes survived until they were mutated to normal nodes, which happened shortly after preprocessing on other platforms. This modification lowers these nodes at the same phase while properly utilizing the chain.5

    Submitted by: Drew Wock <drew.wock@sas.com>
    Reviewed by: Craig Topper, Kevin P. Neal
    Approved by: Craig Topper
    Differential Revision: https://reviews.llvm.org/D63271 (detail/ViewSVN)
    by kpn
  9. [AMDGPU] gfx1010 BoolReg definition. NFC.

    Earlier commit has added AMDGPUOperand::isBoolReg(). Turns out
    gcc issues warning about unused function since D63204 is not
    yet submitted.

    Added NFC part of D63204 to have a use of that function and
    mute the warning. (detail/ViewSVN)
    by rampitec
  10. Reland: [Remarks] Refactor optimization remarks setup

    * Add a common function to setup opt-remarks
    * Rename common options to the same names
    * Add error types to distinguish between file errors and regex errors (detail/ViewSVN)
    by thegameg
  11. [AMDGPU] Enable the implicit arguments for HIP (CLANG)

    Enable 48-bytes of implicit arguments for HIP as well. Earlier it was enabled for OpenCL. This code is specific to AMDGPU target.

    Differential Revision: https://reviews.llvm.org/D62244 (detail/ViewSVN)
    by yaxunl
  12. [x86] move vector shift tests for PR37428; NFC

    As suggested in the post-commit thread for rL363392 - it's
    wasteful to have so many runs for larger tests. AVX1/AVX2
    is what shows the diff and probably what matters most going
    forward. (detail/ViewSVN)
    by spatel
  13. GlobalISel: Avoid producing Illegal copies in RegBankSelect

    Avoid producing illegal register bank copies for reg_sequence and
    phi. The default implementation assumes it is possible to pick any
    operand's bank and use that for the result, introducing a copy for
    operands with a different bank. This does not check for illegal
    copies. It is not legal to introduce a VGPR->SGPR copy, so any VGPR
    operand requires the result to be a VGPR.

    The changes in getInstrMappingImpl aren't strictly necessary, since
    AMDGPU now just bypasses this for reg_sequence/phi. This could be
    replaced with an assert in case other targets run into this. It is
    currently responsible for producing the error for unsatisfiable
    copies, but this will be better served with a verifier check.

    For phis, for now assume any undetermined operands must be
    VGPRs. Eventually, this needs to be able to defer mapping these
    operations. This also does not yet have a way to check for whether the
    block is in a divergent region. (detail/ViewSVN)
    by arsenm
  14. [CodeGenPrepare] propagate debuginfo when copying a shuffle (detail/ViewSVN)
    by spatel
  15. [Attributor] Disable the Attributor by default and fix a comment (detail/ViewSVN)
    by jdoerfert
  16. [Attributor] Introduce bit-encodings for abstract states

    Summary:
    The IntegerState, and its sepecialization BooleanState, can be used to
    simplify the implementation of abstract attributes. The two abstract
    state implementations provide storage and helpers to deal with bit-wise
    encoded state.

    Subscribers: hiraditya, bollu, llvm-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D60012 (detail/ViewSVN)
    by jdoerfert
  17. AMDGPU: Fold readlane intrinsics of constants

    I'm not 100% sure about this, since I'm worried about IR transforms
    that might end up introducing divergence downstream once replaced with
    a constant, but I haven't come up with an example yet. (detail/ViewSVN)
    by arsenm
  18. [ARM] Add MVE horizontal accumulation instructions

    This is the family of vector instructions that combine all the lanes
    in their input vector(s), and output a value in one or two GPRs.

    Differential Revision: https://reviews.llvm.org/D62670 (detail/ViewSVN)
    by miyuki
  19. Revert "Revert r363377: [yaml2obj] - Allow setting custom section types for implicit sections."

    LLD test case will be fixed in a following commit.

    Original commit message:

    [yaml2obj] - Allow setting custom section types for implicit sections.

    We were hardcoding the final section type for sections that
    are usually implicit. The patch fixes that.

    This also fixes a few issues in existent test cases and removes
    one precompiled object.

    Differential revision: https://reviews.llvm.org/D63267 (detail/ViewSVN)
    by grimar

Started by an SCM change (15 times)

This run spent:

  • 2 hr 49 min waiting;
  • 3 hr 29 min build duration;
  • 6 hr 18 min total from scheduled to completion.
LLVM/Clang Warnings: 3 warnings.

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

Missing test results

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

Ninja target failed

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