Started 5 days 11 hr ago
Took 3 hr 16 min on green-dragon-16

Failed Build rL:371818 - C:371817 - #576 (Sep 13, 2019 12:48:14 AM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 371818
  • http://llvm.org/svn/llvm-project/cfe/trunk : 371817
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 371758
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 364589
  • http://llvm.org/svn/llvm-project/zorg/trunk : 371690
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 371763
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 371773
Changes
  1. [AArch64] MachineCombiner FMA matching. NFC.

    Follow-up of rL371321 that added some more FP16 FMA patterns, and an attempt to
    reduce the copy-pasting and make this more readable.

    Differential Revision: https://reviews.llvm.org/D67403 (detail/ViewSVN)
    by sjoerdmeijer
  2. For PR17164: split -fno-lax-vector-conversion into three different
    levels:

    -- none: no lax vector conversions [new GCC default]
    -- integer: only conversions between integer vectors [old GCC default]
    -- all: all conversions between same-size vectors [Clang default]

    For now, Clang still defaults to "all" mode, but per my proposal on
    cfe-dev (2019-04-10) the default will be changed to "integer" as soon as
    that doesn't break lots of testcases. (Eventually I'd like to change the
    default to "none" to match GCC and general sanity.)

    Following GCC's behavior, the driver flag -flax-vector-conversions is
    translated to -flax-vector-conversions=integer.

    This reinstates r371805, reverted in r371813, with an additional fix for
    lldb. (detail/ViewSVN)
    by rsmith

Started by an SCM change (2 times)

This run spent:

  • 1 hr 41 min waiting;
  • 3 hr 16 min build duration;
  • 4 hr 57 min total from scheduled to completion.
LLVM/Clang Warnings: 2 warnings.
Test Result (2 failures / ±0)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

Ninja target failed

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

Compile Error

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