Started 7 hr 6 min ago
Took 1 hr 4 min on green-dragon-17

Failed Build rL:372186 - C:372187 - #646 (Sep 17, 2019 3:37:06 PM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 372186
  • http://llvm.org/svn/llvm-project/cfe/trunk : 372187
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 372143
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 364589
  • 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 : 372128
Changes
  1. [ARM] Update clang for removal of vfp2d16 and vfp2d16sp

    Matching fix for https://reviews.llvm.org/D67375 (r372186).

    Differential Revision: https://reviews.llvm.org/D67467 (detail/ViewSVN)
    by efriedma
  2. [ARM] VFPv2 only supports 16 D registers.

    r361845 changed the way we handle "D16" vs. "D32" targets; there used to
    be a negative "d16" which removed instructions from the instruction set,
    and now there's a "d32" feature which adds instructions to the
    instruction set.  This is good, but there was an oversight in the
    implementation: the behavior of VFPv2 was changed.  In particular, the
    "vfp2" feature was changed to imply "d32". This is wrong: VFPv2 only
    supports 16 D registers.

    In practice, this means if you specify -mfpu=vfpv2, the compiler will
    generate illegal instructions.

    This patch gets rid of "vfp2d16" and "vfp2d16sp", and fixes "vfp2" and
    "vfp2sp" so they don't imply "d32".

    Differential Revision: https://reviews.llvm.org/D67375 (detail/ViewSVN)
    by efriedma
  3. Revert "Create UsersManual section entitled 'Controlling Floating Point"

    This reverts commit a08d5a4b0ebd44dc64f41049ed4e97a3c6d31498. (detail/ViewSVN)
    by erichkeane

Started by an SCM change (2 times)

This run spent:

  • 1 hr 5 min waiting;
  • 1 hr 4 min build duration;
  • 2 hr 9 min total from scheduled to completion.
LLVM/Clang Warnings: 2 warnings.

Identified problems

Assertion failure

This build failed because of an assertion failure. Below is a list of all errors in the build log:
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

Missing test results

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

Regression test failed

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

Ninja target failed

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