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

Failed Build #14190 (Jun 8, 2019 6:01:02 AM)

  • : 362875
  • : 362856
  • : 362859
  • : 362745
  • : 362851
  • : 362866
  • : 362811
  1. [NFC] Added tests for D63038 (detail)
    by xbolva00
  2. [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

    Differential Revision: (detail)
    by dmgreen
  3. [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 /

    Differential Revision: (detail)
    by dmgreen
  4. [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: (detail)
    by dmgreen
  5. [ARM] Add extra gep costmodel tests for MVE and half float. NFC (detail)
    by dmgreen
  6. [ARM] Add HasNEON for all Neon patterns in NFCI

    We are starting to add an entirely separate vector architecture to the ARM
    backend. To do that we need at least some separation between the existing NEON
    and the new MVE code. This patch just goes through the Neon patterns and
    ensures that they are predicated on HasNEON, giving MVE a stable place to start

    No tests yet as this is largely an NFC, and we don't have the other target that
    will treat any of these intructions as legal.

    Differential Revision: (detail)
    by dmgreen

Started by timer (5 times)

This run spent:

  • 4 hr 50 min waiting;
  • 4 hr 57 min build duration;
  • 9 hr 47 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