Started 2 mo 16 days ago
Took 1 hr 36 min

Unstable Build clang-r362874-t57350-b57350.tar.gz (Jun 8, 2019 5:39:55 AM)

Issues

Found 8 issues:
Warning: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
[Pipeline] // dir
[Pipeline] dir
Running in /Users/buildslave/jenkins/workspace/test-suite-verify-machineinstrs-x86_64h-O3/pseudo-checkout-llvm
[Pipeline] {
[Pipeline] checkout
WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
[Pipeline] }
[Pipeline] // dir
Warning: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
Cleaning local Directory trunk
Checking out http://llvm.org/svn/llvm-project/llvm/trunk at revision 362874
 U        .
At revision 362874

WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
No changes for http://llvm.org/svn/llvm-project/cfe/trunk since the previous build
[Pipeline] }
Warning: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
Cleaning local Directory trunk
Checking out http://llvm.org/svn/llvm-project/cfe/trunk at revision 362874
 U        .
At revision 362874

WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
No changes for http://llvm.org/svn/llvm-project/clang-tools-extra/trunk since the previous build
[Pipeline] }
Warning: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
Checking out a fresh workspace because /Users/buildslave/jenkins/workspace/test-suite-verify-machineinstrs-x86_64h-O3/pseudo-checkout-clang-tools-extra/trunk doesn't exist
Cleaning local Directory trunk
Checking out http://llvm.org/svn/llvm-project/clang-tools-extra/trunk at revision 362874
At revision 362874

WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
No changes for http://llvm.org/svn/llvm-project/compiler-rt/trunk since the previous build
[Pipeline] }
Warning: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
Cleaning local Directory trunk
Checking out http://llvm.org/svn/llvm-project/compiler-rt/trunk at revision 362874
 U        .
At revision 362874

WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
No changes for http://llvm.org/svn/llvm-project/libcxx/trunk since the previous build
[Pipeline] }
Warning: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
Cleaning local Directory trunk
Checking out http://llvm.org/svn/llvm-project/libcxx/trunk at revision 362874
 U        .
At revision 362874

WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
Checking out a fresh workspace because /Users/buildslave/jenkins/workspace/test-suite-verify-machineinstrs-x86_64h-O3/lnt doesn't exist
Cleaning local Directory .
Warning: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
A         examples
A         examples/functions.py
A         examples/run_to_csv.py
At revision 362875

WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
Updating http://llvm.org/svn/llvm-project/test-suite/trunk at revision '2019-06-08T05:39:55.292 -0700'
At revision 362875
Warning: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
+ config/tasks/task jenkinsrun config/tasks/test-suite-verify-machineinstrs.sh -a compiler=http://labmaster2.local/artifacts/clang-stage1-configure-RA/clang-r362874-t57350-b57350.tar.gz -D 'CMAKE_FLAGS= -C ../config/tasks/cmake/caches/target-x86_64h-macos.cmake -C ../config/tasks/cmake/caches/opt-O3.cmake'
+ export PATH=/Users/buildslave/jenkins/workspace/test-suite-verify-machineinstrs-x86_64h-O3/config/tasks/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin
+ PATH=/Users/buildslave/jenkins/workspace/test-suite-verify-machineinstrs-x86_64h-O3/config/tasks/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin
+ build clean
...removing 'test-suite-build'
WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
...removing 'pseudo-checkout-compiler-rt'
...removing 'pseudo-checkout-llvm'

Build Log

Revision: 362564
Changes
  1. [ARM] Adjust isLegalT1AddressImmediate for non-legal types

    Types such as float and i64's do not have legal loads in Thumb1, but will still
    be loaded with a LDR (or potentially multiple LDR's). As such we can treat the
    cost of addressing mode calculations the same as an i32 and get some optimisation
    benefits.

    Differential Revision: https://reviews.llvm.org/D62968 (detail)
    by dmgreen
  2. [ARM] Add MVE addressing to isLegalT2AddressImmediate

    Now with MVE being added, we can add the vector addressing mode costs for it.
    These are generally imm7 multiplied by the size of the type being loaded /
    stored.

    Differential Revision: https://reviews.llvm.org/D62967 (detail)
    by dmgreen
  3. [ARM] Add fp16 addressing to isLegalT2AddressImmediate

    The fp16 version of VLDR takes a imm8 multiplied by 2. This updates the costs
    to account for those, and adds extra testing. It is dependant upon hasFPRegs16
    as this is what the load/store instructions require.

    Differential Revision: https://reviews.llvm.org/D62966 (detail)
    by dmgreen

Started by upstream project relay-test-suite-verify-machineinstrs build number 5400
originally caused by:

This run spent:

  • 1 hr 11 min waiting;
  • 1 hr 36 min build duration;
  • 1 hr 36 min total from scheduled to completion.

Identified problems

No identified problem

No problems were identified. If you know why this problem occurred, please add a suitable Cause for it.