Started 1 mo 2 days ago
Took 4 hr 28 min on green-dragon-02

Failed Build #14722 (Sep 18, 2019 4:54:25 AM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 372215
  • http://llvm.org/svn/llvm-project/cfe/trunk : 372203
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 372205
  • http://llvm.org/svn/llvm-project/zorg/trunk : 371835
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 372034
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 372206
Changes
  1. Fix -Wdocumentation warning. NFCI. (detail)
    by rksimon
  2. Fix -Wdocumentation "empty paragraph passed to '\brief'" warning. NFCI. (detail)
    by rksimon
  3. Fix -Wdocumentation "@returns in a void function" warning. NFCI. (detail)
    by rksimon
  4. Fix -Wdocumentation "Unknown param" warning. NFCI. (detail)
    by rksimon
  5. [cmake] Changes to get Windows self-host working with PGO

    Fixes quoting of profile arguments to work on Windows
    Suppresses adding profile arguments to linker flags when using lld-link
    Avoids -fprofile-instr-use being added to rc.exe flags
    Removes duplicated adding of -fprofile-instr-use to linker flags (since
    r355541)
    Move handling LLVM_PROFDATA_FILE to HandleLLVMOptions.cmake

    Differential Revision: https://reviews.llvm.org/D62063 (detail)
    by russell_gallop
  6. [AMDGPU] Allow FP inline constant in v_madak_f16 and v_fmaak_f16

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

    Change-Id: Ic38f47cb2079c2c1070a441b5943854844d80a7c (detail)
    by tpr
  7. [Alignment] Add a None() member function

    Summary:
    This will allow writing `if(A != llvm::Align::None())` which is clearer than `if(A > llvm::Align(1))`

    This is patch is part of a series to introduce an Alignment type.
    See this thread for context: http://lists.llvm.org/pipermail/llvm-dev/2019-July/133851.html
    See this patch for the introduction of the type: https://reviews.llvm.org/D64790

    Reviewers: courbet

    Subscribers: llvm-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D67697 (detail)
    by gchatelet
  8. [clang-tidy] Fix a potential infinite loop in readability-isolate-declaration check.

    Reviewers: ilya-biryukov

    Subscribers: xazax.hun, cfe-commits

    Tags: #clang

    Differential Revision: https://reviews.llvm.org/D67654 (detail)
    by hokein
  9. tsan: allow the Go runtime to return multiple stack frames for a single PC

    This fix allows tsan to report stack traces correctly even in the
    presence of mid-stack inlining by the Go compiler.

    See https://go-review.googlesource.com/c/go/+/195781 for the Go runtime side of this change.

    Author: randall77 (Keith Randall)
    Reviewed: https://reviews.llvm.org/D67671 (detail)
    by dvyukov
  10. [AArch64][DebugInfo] Do not recompute CalleeSavedStackSize

    This patch fixes a bug exposed by D65653 where a subsequent invocation
    of `determineCalleeSaves` ends up with a different size for the callee
    save area, leading to different frame-offsets in debug information.

    In the invocation by PEI, `determineCalleeSaves` tries to determine
    whether it needs to spill an extra callee-saved register to get an
    emergency spill slot. To do this, it calls 'estimateStackSize' and
    manually adds the size of the callee-saves to this. PEI then allocates
    the spill objects for the callee saves and the remaining frame layout
    is calculated accordingly.

    A second invocation in LiveDebugValues causes estimateStackSize to return
    the size of the stack frame including the callee-saves. Given that the
    size of the callee-saves is added to this, these callee-saves are counted
    twice, which leads `determineCalleeSaves` to believe the stack has
    become big enough to require spilling an extra callee-save as emergency
    spillslot. It then updates CalleeSavedStackSize with a larger value.

    Since CalleeSavedStackSize is used in the calculation of the frame
    offset in getFrameIndexReference, this leads to incorrect offsets for
    variables/locals when this information is recalculated after PEI.

    Reviewers: omjavaid, eli.friedman, thegameg, efriedma

    Reviewed By: efriedma

    Differential Revision: https://reviews.llvm.org/D66935 (detail)
    by s.desmalen
  11. [lldb] Print better diagnostics for user expressions and modules

    Summary:
    Currently our expression evaluators only prints very basic errors that are not very useful when writing complex expressions.

    For example, in the expression below the user made a type error, but it's not clear from the diagnostic what went wrong:
    ```
    (lldb) expr printf("Modulos are:", foobar%mo1, foobar%mo2, foobar%mo3)
    error: invalid operands to binary expression ('int' and 'double')
    ```

    This patch enables full Clang diagnostics in our expression evaluator. After this patch the diagnostics for the expression look like this:

    ```
    (lldb) expr printf("Modulos are:", foobar%mo1, foobar%mo2, foobar%mo3)
    error: <user expression 1>:1:54: invalid operands to binary expression ('int' and 'float')
    printf("Modulos are:", foobar%mo1, foobar%mo2, foobar%mo3)
                                                   ~~~~~~^~~~
    ```

    To make this possible, we now emulate a user expression file within our diagnostics. This prevents that the user is exposed to
    our internal wrapper code we inject.

    Note that the diagnostics that refer to declarations from the debug information (e.g. 'note' diagnostics pointing to a called function)
    will not be improved by this as they don't have any source locations associated with them, so caret or line printing isn't possible.
    We instead just suppress these diagnostics as we already do with warnings as they would otherwise just be a context message
    without any context (and the original diagnostic in the user expression should be enough to explain the issue).

    Fixes rdar://24306342

    Reviewers: JDevlieghere, aprantl, shafik, #lldb

    Reviewed By: JDevlieghere, #lldb

    Subscribers: usaxena95, davide, jingham, aprantl, arphaman, kadircet, lldb-commits

    Tags: #lldb

    Differential Revision: https://reviews.llvm.org/D65646 (detail)
    by Raphael Isemann
  12. Revert "r372201: [Support] Replace function with function_ref in writeFileAtomically. NFC"

    function_ref causes calls to the function to be ambiguous, breaking
    compilation.

    Reverting for now. (detail)
    by ibiryukov
  13. [Support] Replace function with function_ref in writeFileAtomically. NFC

    Summary:
    The latter is slightly more efficient and communicates the intent of the
    API: writeFileAtomically does not own or copy the callback, it merely
    calls it at some point.

    Reviewers: jkorous

    Reviewed By: jkorous

    Subscribers: hiraditya, dexonsmith, jfb, llvm-commits, cfe-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D67584 (detail)
    by ibiryukov

Started by timer (4 times)

This run spent:

  • 3 hr 43 min waiting;
  • 4 hr 28 min build duration;
  • 8 hr 11 min total from scheduled to completion.

Identified problems

Missing test results

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

Regression test failed

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

Ninja target failed

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