Started 26 days ago
Took 4 hr 21 min on green-dragon-02

Failed Build #14922 (Oct 20, 2019 7:30:33 PM)

  • : 375384
  • : 375362
  • : 375317
  • : 375353
  • : 375340
  • : 375316
  1. [Attributor][FIX] Silence sign-compare warning (detail)
    by jdoerfert
  2. [Attributor] Teach AANoCapture to use information in-flight more aggressively

    AAReturnedValues, AAMemoryBehavior, and AANoUnwind, can provide
    information that helps during the tracking or even justifies no-capture.
    We now use this information and enable no-capture in some test cases
    designed a long while a ago for these cases. (detail)
    by jdoerfert
  3. [X86] Check Subtarget.hasSSE3() before calling shouldUseHorizontalOp and emitting X86ISD::FHADD in LowerUINT_TO_FP_i64.

    This was a regression from r375341.

    Fixes PR43729. (detail)
    by ctopper
  4. [IndVars] Add a todo to reflect a further oppurtunity identified in D69009

    Nikita pointed out an oppurtunity, might as well document it in the code. (detail)
    by reames
  5. [IndVars] Eliminate loop exits with equivalent exit counts

    We can end up with two loop exits whose exit counts are equivalent, but whose textual representation is different and non-obvious. For the sub-case where we have a series of exits which dominate one another (common), eliminate any exits which would iterate *after* a previous exit on the exiting iteration.

    As noted in the TODO being removed, I'd always thought this was a good idea, but I've now seen this in a real workload as well.

    Interestingly, in review, Nikita pointed out there's let another oppurtunity to leverage SCEV's reasoning.  If we kept track of the min of dominanting exits so far, we could discharge exits with EC >= MDE.  This is less powerful than the existing transform (since later exits aren't considered), but potentially more powerful for any case where SCEV can prove a >= b, but neither a == b or a > b.  I don't have an example to illustrate that oppurtunity, but won't be suprised if we find one and return to handle that case as well. 

    Differential Revision: (detail)
    by reames

Started by timer (4 times)

This run spent:

  • 3 hr 20 min waiting;
  • 4 hr 21 min build duration;
  • 7 hr 42 min total from scheduled to completion.

Identified problems

Ninja target failed

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

Regression test failed

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

Missing test results

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