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

Failed Build #14200 (Jun 10, 2019 7:52:04 AM)

  • : 362943
  • : 362924
  • : 362859
  • : 362745
  • : 362851
  • : 362866
  • : 362939
  1. [InstCombine] change canonicalization to fabs() to use FMF on fsub

    Similar to rL362909:
    This isn't the ideal fix (use FMF on the select), but it's still an
    improvement until we have better FMF propagation to selects and other
    FP math operators.

    I don't think there's much risk of regression from this change by
    not including the FMF on the fcmp any more. The nsz/nnan FMF
    should be the same on the fcmp and the fsub because they have the
    same operand. (detail)
    by spatel
  2. [ARM] Disallow PC, and optionally SP, in VMOVRH and VMOVHR.

    Arm v8.1-M supports the VMOV instructions that move a half-precision
    value to and from a GPR, but not if the GPR is SP or PC.

    To fix this, I've changed those instructions to use the rGPR register
    class instead of GPR. rGPR always excludes PC, and it excludes SP
    except in the presence of the HasV8Ops target feature (i.e. Arm v8-A).
    So the effect is that VMOV.F16 to and from PC is now illegal
    everywhere, but VMOV.F16 to and from SP is illegal only on non-v8-A
    cores (which I believe is all as it should be).

    Reviewers: dmgreen, samparker, SjoerdMeijer, ostannard

    Reviewed By: ostannard

    Subscribers: ostannard, javed.absar, kristof.beyls, hiraditya, llvm-commits

    Tags: #llvm

    Differential Revision: (detail)
    by statham
  3. [ExecutionEngine] Add UnaryOperator visitor to the interpreter

    This is to support the unary FNeg instruction.

    Differential Revision: (detail)
    by mcinally
  4. [yaml2obj] - Remove TODOs from dynsymtab-implicit-sections-size-content.yaml. NFCI.

    Now when is fixed,
    we can remove these TODOs. (detail)
    by grimar
  5. [clangd] Revamp textDocument/onTypeFormatting.

    The existing implementation (which triggers on }) is fairly simple and
    has flaws:
    - doesn't trigger frequently/regularly enough (particularly in editors that type the }
    for you)
    - often reformats too much code around the edit
    - has jarring cases that I don't have clear ideas for fixing

    This implementation is designed to trigger on newline, which feels to me more
    intuitive than } or ;.
    It does have allow for reformatting after other characters - it has a
    basic behavior and a model for adding specialized behavior for
    particular characters. But at least initially I'd stick to advertising
    \n in the capabilities.

    This also handles comment splitting: when you insert a line break inside
    a line comment, it will make the new line into an aligned line comment.

    Working on tests, but want people to patch it in and try it - it's hard to
    see if "feel" is right purely by looking at a test.

    Reviewers: ilya-biryukov, hokein

    Subscribers: mgorny, ioeric, MaskRay, jkorous, arphaman, kadircet, cfe-commits

    Tags: #clang

    Differential Revision: (detail)
    by sammccall
  6. [llvm-readobj/llvm-readelf] - Don't fail to dump the object if .dynsym has broken sh_link field.

    This is

    GNU readelf allows to dump the objects in that case,
    but llvm-readobj/llvm-readelf reports an error and stops.

    The patch fixes that.

    Differential revision: (detail)
    by grimar
  7. [InstCombine] allow unordered preds when canonicalizing to fabs()

    PR42179: (detail)
    by spatel
  8. [InstCombine] add tests for fcmp unordered pred -> fabs (PR42179); NFC (detail)
    by spatel
  9. [MCA] Fix -Wunused-private-field warning after r362933. NFC

    This should unbreak the buildbots. (detail)
    by adibiagio
  10. [clangd] Stop marshalling/requiring FormattingOptions. We never did anything with them. (detail)
    by sammccall
  11. [MCA] Further refactor the bottleneck analysis view. NFCI. (detail)
    by adibiagio
  12. gn build: Merge r362913 (detail)
    by nico
  13. [yaml2obj/obj2yaml] - Make RawContentSection::Content and RawContentSection::Size optional

    This is a follow-up for D62809.

    Content and Size fields should be optional as was discussed in comments
    of the D62809's thread. With that, we can describe a specific string table and
    symbol table sections in a more correct way and also show appropriate errors.

    The patch adds lots of test cases where the behavior is described in details.

    Differential revision: (detail)
    by grimar
  14. [yaml2obj] - Do not assert when .dynsym is specified explicitly, but .dynstr is not present.

    We have a code in buildSectionIndex() that adds implicit sections:

    // Add special sections after input sections, if necessary.
    for (StringRef Name : implicitSectionNames())
      if (SN2I.addName(Name, SecNo)) {
        // Account for this section, since it wasn't in the Doc

    The problem arises when .dynsym is specified explicitly and no
    DynamicSymbols is used. In that case, we do not add
    .dynstr implicitly and will assert later when will try to set Link
    for .dynsym.

    Seems, in this case, reasonable behavior is to allow Link field to be zero.
    This is what this patch does.

    Differential revision: (detail)
    by grimar
  15. [ARM] Enable Unroll UpperBound

    This option allows loops with small max trip counts to be fully unrolled. This
    can help with code like the remainder loops from manually unrolled loops like
    those that appear in the cmsis dsp library. We would apparently previously
    runtime unroll them with the default unroll count (4).

    Differential Revision: (detail)
    by dmgreen
  16. Fix MSVC "32-bit shift implicitly converted to 64 bits" warning. NFCI. (detail)
    by rksimon

Started by timer (5 times)

This run spent:

  • 4 hr 41 min waiting;
  • 4 hr 57 min build duration;
  • 9 hr 38 min total from scheduled to completion.
Test Result (1 failure / ±0)

Identified problems

Compile Error

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

Ninja target failed

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

Regression test failed

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