Started 4 mo 11 days ago
Took 9 hr 39 min on green-dragon-13

Failed Build #6422 (Jun 9, 2019 5:06:11 AM)

  • : 362900
  • : 362887
  • : 362859
  • : 362745
  • : 362866
  • : 362811
  1. [CaptureTracking] Don't let comparisons against null escape inbounds pointers

    Pointers that are in-bounds (either through dereferenceable_or_null or
    thorough a getelementptr inbounds) cannot be captured with a comparison
    against null. There is no way to construct a pointer that is still in
    bounds but also NULL.

    This helps safe languages that insert null checks before load/store
    instructions. Without this patch, almost all pointers would be
    considered captured even for simple loads. With this patch, an icmp with
    null will not be seen as escaping as long as certain conditions are met.

    There was a lot of discussion about this patch. See the Phabricator
    thread for detals.

    Differential Revision: (detail)
    by aykevl
  2. [bindings/go] Add wrappers for atomic operations.

    This patch adds Go bindings for atomic operations in LLVM.

    Differential Revision: (detail)
    by aykevl
  3. [X86] NFCI : Comment updation for EVEX to VEX translation.

    Reviewers: llvm-commits, jbhateja

    Reviewed By: jbhateja

    Subscribers: llvm-commits

    Tags: #llvm

    Differential Revision: (detail)
    by Jatin Bhateja
  4. Use for-range loop. NFCI. (detail)
    by rksimon
  5. [AArch64][GlobalISel] Select immediate forms of cmp instructions.

    A simple re-use of the immediate operand matcher and renderer functions.

    rdar://43795178 (detail)
    by aemerson
  6. [X86] Remove (store (f32 (extractelt (v4f32))) isel patterns which is redundant.

    We emit a MOVSSmr and a COPY_TO_REGCLASS, but that's what we would get from
    selecting the store and extractelt independently. (detail)
    by ctopper

Started by upstream project clang-stage2-cmake-RgSan_relay build number 1137
originally caused by:

This run spent:

  • 2 ms waiting;
  • 9 hr 39 min build duration;
  • 9 hr 39 min total from scheduled to completion.
Test Result (no failures)

    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