Started 4 mo 0 days ago
Took 31 min on green-dragon-23

Success Build #2968 (Aug 7, 2019 2:17:05 PM)

Build Artifacts
test_logs.tgz48.91 KB view
Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 368207
  • http://llvm.org/svn/llvm-project/cfe/trunk : 368202
  • http://llvm.org/svn/llvm-project/lldb/trunk : 368208
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 364589
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 368088
Changes
  1. [CommandObject] Remove unused function (detail)
    by Jonas Devlieghere
  2. [X86] Add test cases for missed opportunities to use pack instructions for 512->256 truncates with prefer-vector-width=256

    If the 512-bit vectors are going to be split anyway, then we are
    better off using pack to implicitly concatenate the 256 bit pieces. (detail)
    by ctopper
  3. [Symbol] Remove commented out code from CompileUnit (detail)
    by xiaobai
  4. Revert r367501 "Create unique, but identically-named ELF sections..."

    This reverts commit fbc563e2cb6c5f1d0200b390513506b6aca4d2e9 "Create
    unique, but identically-named ELF sections for explicitly-sectioned
    functions and globals when using -function-sections and
    -data-sections."

    Reason for revert: sections are created with potentially wrong
    attributes. (detail)
    by inglorion
  5. Add target requirements for those bots which don't handle x86. (detail)
    by void
  6. [NFC] Fixed newly added tests (detail)
    by xbolva00
  7. [NFC] Added tests for x/fabs(X) fold (detail)
    by xbolva00
  8. Add support for deterministically linked binaries on macOS to lldb.

    When ld64 links a binary deterministically using the flag ZERO_AR_DATE,
    it sets a timestamp of 0 for N_OSO members in the symtab section, rather
    than the usual last modified date of the object file. Prior to this
    patch, lldb would compare the timestamp from the N_OSO member against
    the last modified date of the object file, and skip loading the object
    file if there was a mismatch. This patch updates the logic to ignore the
    timestamp check if the N_OSO member has timestamp 0.

    The original logic was added in https://reviews.llvm.org/rL181631 as a
    safety check to avoid problems when debugging if the object file was out
    of date. This was prior to the introduction of deterministic build in
    ld64. lld still doesn't support deterministic build.

    Other code in llvm already relies on and uses the assumption that a
    timestamp of 0 means deterministic build. For example, commit
    9ccfddc39d4d27f9b16fcc72ab30d483151d6d08 adds similar timestamp checking
    logic to dsymutil, but special cases timestamp 0. Likewise, commit
    0d1bb79a0413f221432a7b1d0d2d10c84c4bbb99 adds a long comment describing
    deterministic archive, which mostly uses timestamp 0 for determinism.

    Patch from Erik Chen <erikchen@chromium.org>!

    Differential Revision: https://reviews.llvm.org/D65826 (detail)
    by nico

Started by upstream project lldb-cmake build number 32889
originally caused by:

  • Started by timer

Started by upstream project lldb-cmake build number 32890
originally caused by:

  • Started by timer

Started by upstream project lldb-cmake build number 32891
originally caused by:

  • Started by timer

Started by upstream project lldb-cmake build number 32892
originally caused by:

  • Started by timer

Started by upstream project lldb-cmake build number 32893
originally caused by:

  • Started by timer

Started by upstream project lldb-cmake build number 32894
originally caused by:

  • Started by timer

Started by upstream project lldb-cmake build number 32895
originally caused by:

  • Started by timer

This run spent:

  • 1 hr 45 min waiting;
  • 31 min build duration;
  • 2 hr 16 min total from scheduled to completion.
Test Result (no failures)