Started 4 days 16 hr ago
Took 4 hr 25 min on green-dragon-02

Failed Build #14670 (Sep 11, 2019 3:24:00 AM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 371598
  • http://llvm.org/svn/llvm-project/cfe/trunk : 371598
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 371598
  • 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. Revert "clang-misexpect: Profile Guided Validation of Performance Annotations in LLVM"

    This reverts commit r371584. It introduced a dependency from compiler-rt
    to llvm/include/ADT, which is problematic for multiple reasons.

    One is that it is a novel dependency edge, which needs cross-compliation
    machinery for llvm/include/ADT (yes, it is true that right now
    compiler-rt included only header-only libraries, however, if we allow
    compiler-rt to depend on anything from ADT, other libraries will
    eventually get used).

    Secondly, depending on ADT from compiler-rt exposes ADT symbols from
    compiler-rt, which would cause ODR violations when Clang is built with
    the profile library. (detail)
    by gribozavr
  2. [ARM] Take into account -mcpu and -mfpu options while handling 'crypto' feature

    Submittin in behalf of krisb (Kristina Bessonova) <ch.bessonova@gmail.com>

    Summary:
    '+crypto' means '+aes' and '+sha2' for arch >= ARMv8 when they were
    not disabled explicitly. But this is correctly handled only in case of
    '-march' option, though the feature may also be specified through
    the '-mcpu' or '-mfpu' options. In the following example:

      $ clang -mcpu=cortex-a57 -mfpu=crypto-neon-fp-armv8

    'aes' and 'sha2' are disabled that is quite unexpected:

      $ clang -cc1 -triple armv8--- -target-cpu cortex-a57
        <...> -target-feature -sha2 -target-feature -aes -target-feature +crypto

    This exposed by https://reviews.llvm.org/D63936 that makes
    the 'aes' and 'sha2' features disabled by default.

    So, while handling the 'crypto' feature we need to take into account:
      - a CPU name, as it provides the information about architecture
        (if no '-march' option specified),
      - features, specified by the '-mcpu' and '-mfpu' options.

    Reviewers: SjoerdMeijer, ostannard, labrinea, dnsampaio

    Reviewed By: dnsampaio

    Subscribers: ikudrin, javed.absar, kristof.beyls, cfe-commits

    Tags: #clang

    Differential Revision: https://reviews.llvm.org/D66018

    Author: krisb (detail)
    by dnsampaio
  3. [LoopInterchange] Properly move condition, induction increment and ops to latch.

    Currently we only rely on the induction increment to come before the
    condition to ensure the required instructions get moved to the new
    latch.

    This patch duplicates and moves the required instructions to the
    newly created latch. We move the condition to the end of the new block,
    then process its operands. We stop at operands that are defined
    outside the loop, or are the induction PHI.

    We duplicate the instructions and update the uses in the moved
    instructions, to ensure other users remain intact. See the added
    test2 for such an example.

    Reviewers: efriedma, mcrosier

    Reviewed By: efriedma

    Differential Revision: https://reviews.llvm.org/D67367 (detail)
    by fhahn
  4. [NFC][ARM] Add and modify tests

    Add test for ParallelDSP. (detail)
    by sam_parker
  5. [LTO] Avoid calling GlobalValue::getGUID (MD5) twice (detail)
    by maskray
  6. [TLI][AMDGPU] AMDPAL does not have library functions

    Configure TLI to say that r600/amdgpu does not have any library
    functions, such that InstCombine does not do anything like turn sin/cos
    into the library function @tan with sufficient fast math flags.

    Differential Revision: https://reviews.llvm.org/D67406

    Change-Id: I02f907d3e64832117ea9800e9f9285282856e5df (detail)
    by tpr
  7. [llvm-objcopy] Simplify --prefix-alloc-sections

    Handle --prefix-alloc-sections after --rename-sections so that --prefix-alloc-sections code
    does not have to check if renaming has been performed.

    Reviewed By: jhenderson

    Differential Revision: https://reviews.llvm.org/D66931 (detail)
    by maskray
  8. [Attributor] Implement "noalias" callsite argument deduction

    Summary: Now, `nocapture` is deduced in Attributor therefore, this patch introduces deduction for `noalias` callsite argument using `nocapture`.

    Reviewers: jdoerfert, sstefan1

    Reviewed By: jdoerfert

    Subscribers: lebedev.ri, hiraditya, llvm-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D67286 (detail)
    by uenoku
  9. [Attributor][Fix] Manifest nocapture only in CSArgument or Argument

    Summary:
    We can query to Attributor whether the value is captured in the scope or not on the following way:

    ```
        const auto & NoCapAA = A.getAAFor<AANoCapture>(*this, IRPosition::value(V));
    ```
    And if V is CallSiteReturned then `getDeducedAttribute` will add `nocatpure` to the callsite returned value. It is not valid.
    This patch checks the position is an argument or call site argument.

    This is tested in D67286.

    Reviewers: jdoerfert, sstefan1

    Reviewed By: jdoerfert

    Subscribers: hiraditya, llvm-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D67342 (detail)
    by uenoku
  10. [Debuginfo][Instcombiner] Do not clone dbg.declare.

    TryToSinkInstruction() has a bug: While updating debug info for
    sunk instruction, it could clone dbg.declare intrinsic.
    That is wrong. There could be only one dbg.declare.
    The fix is to not clone dbg.declare intrinsic and to update
    it`s arguments, to not to point to sunk instruction.

    Differential Revision: https://reviews.llvm.org/D67217 (detail)
    by avl

Started by timer (6 times)

This run spent:

  • 5 hr 13 min waiting;
  • 4 hr 25 min build duration;
  • 9 hr 38 min total from scheduled to completion.

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

Missing test results

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