Started 5 yr 3 mo ago
Took 1 hr 15 min on green-dragon-14

Build #385 (Aug 14, 2017 3:36:28 AM)

  • : 310827
  • : 310820
  • : 310800
  • : 303903
  • : 310746
  • : 310761
  • : 310821
  1. [llvm-cov] Add an option which maps the location of source directories on another machine to your local copies

    This patch adds the -path-equivalence option (example: llvm-cov show -path-equivalence=/origin/path,/local/path) which maps the source code path from one machine to another when using `llvm-cov show`. This is similar to the -filename-equivalence option, but doesn't require you to specify all the source files on the command line.

    This allows you to generate the coverage data on one machine (e.g. in a CI system), and then use llvm-cov on another machine where you have the same code base on a different path.

    Reviewers: vsk

    Reviewed By: vsk

    Subscribers: llvm-commits

    Differential Revision: (detail)
    by seaneveson
  2. MachineInstr: Reason locally about some memory objects before going to AA.

    This addresses a FIXME in MachineInstr::mayAlias. (detail)
    by bmakam
  3. [LoopUnroll] Enable option to peel remainder loop

    On some targets, the penalty of executing runtime unrolling checks
    and then not the unrolled loop can be significantly detrimental to
    performance. This results in the need to be more conservative with
    the unroll count, keeping a trip count of 2 reduces the overhead as
    well as increasing the chance of the unrolled body being executed. But
    being conservative leaves performance gains on the table.

    This patch enables the unrolling of the remainder loop introduced by
    runtime unrolling. This can help reduce the overhead of misunrolled
    loops because the cost of non-taken branches is much less than the
    cost of the backedge that would normally be executed in the remainder
    loop. This allows larger unroll factors to be used without suffering
    performance loses with smaller iteration counts.

    Differential Revision:
    by sam_parker

Started by timer

This run spent:

  • 25 min waiting;
  • 1 hr 15 min build duration;
  • 1 hr 41 min total from scheduled to completion.
Test Result (no failures)