Started 1 mo 1 day ago
Took 1 hr 3 min on green-dragon-17

Failed Build rL:372378 - C:372368 - #689 (Sep 20, 2019 2:30:41 AM)

  • : 372378
  • : 372368
  • : 372348
  • : 364589
  • : 372342
  • : 372242
  • : 372317
  1. [llvm-dwarfdump] Adjust Windows path to be acceptable by JSON

    Backslash is a special character according to JSON specification,
    so we should avoid that when printing a file path with the
    --statistics option.

    Differential Revision: (detail/ViewSVN)
    by djtodoro
  2. [yaml2obj/obj2yaml] - Do not trigger llvm_unreachable when dumping/parsing relocations and e_machine is unsupported.

    Currently when e_machine is set to something that is not supported by YAML lib,
    then tools fail with llvm_unreachable.

    In this patch I allow them to handle relocations in this case.
    It can be used to dump and create objects for broken or unsupported targets.

    Differential revision: (detail/ViewSVN)
    by grimar
  3. [MachinePipeliner] Improve the TargetInstrInfo API analyzeLoop/reduceLoopCount

    The way MachinePipeliner uses these target hooks is stateful - we reduce trip
    count by one per call to reduceLoopCount. It's a little overfit for hardware
    loops, where we don't have to worry about stitching a loop induction variable
    across prologs and epilogs (the induction variable is implicit).

    This patch introduces a new API:

      /// Analyze loop L, which must be a single-basic-block loop, and if the
      /// conditions can be understood enough produce a PipelinerLoopInfo object.
      virtual std::unique_ptr<PipelinerLoopInfo>
      analyzeLoopForPipelining(MachineBasicBlock *LoopBB) const;

    The return value is expected to be an implementation of the abstract class:

      /// Object returned by analyzeLoopForPipelining. Allows software pipelining
      /// implementations to query attributes of the loop being pipelined.
      class PipelinerLoopInfo {
        virtual ~PipelinerLoopInfo();
        /// Return true if the given instruction should not be pipelined and should
        /// be ignored. An example could be a loop comparison, or induction variable
        /// update with no users being pipelined.
        virtual bool shouldIgnoreForPipelining(const MachineInstr *MI) const = 0;

        /// Create a condition to determine if the trip count of the loop is greater
        /// than TC.
        /// If the trip count is statically known to be greater than TC, return
        /// true. If the trip count is statically known to be not greater than TC,
        /// return false. Otherwise return nullopt and fill out Cond with the test
        /// condition.
        virtual Optional<bool>
        createTripCountGreaterCondition(int TC, MachineBasicBlock &MBB,
                                     SmallVectorImpl<MachineOperand> &Cond) = 0;

        /// Modify the loop such that the trip count is
        /// OriginalTC + TripCountAdjust.
        virtual void adjustTripCount(int TripCountAdjust) = 0;

        /// Called when the loop's preheader has been modified to NewPreheader.
        virtual void setPreheader(MachineBasicBlock *NewPreheader) = 0;

        /// Called when the loop is being removed.
        virtual void disposed() = 0;

    The Pipeliner (ModuloSchedule.cpp) can use this object to modify the loop while
    allowing the target to hold its own state across all calls. This API, in
    particular the disjunction of creating a trip count check condition and
    adjusting the loop, improves the code quality in ModuloSchedule.cpp. (detail/ViewSVN)
    by jamesm
  4. [CallSiteSplitting] Remove unused includes (NFC). (detail/ViewSVN)
    by fhahn

Started by an SCM change (4 times)

This run spent:

  • 53 min waiting;
  • 1 hr 3 min build duration;
  • 1 hr 57 min total from scheduled to completion.
LLVM/Clang Warnings: 2 warnings.

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

Assertion failure

This build failed because of an assertion failure. Below is a list of all errors in the build log:
Indication 3

Missing test results

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

Compile Error

This build failed because of a compile error. Below is a list of all errors in the build log:
Indication 5