Started 1 yr 0 mo ago
Took 28 min on green-dragon-24

Failed Build #83 (Dec 3, 2018 4:20:46 AM)

Build Artifacts
test_logs.tgz125 B view
Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 348122
  • http://llvm.org/svn/llvm-project/cfe/trunk : 348127
  • http://llvm.org/svn/llvm-project/lldb/trunk : 348058
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 347930
Changes
  1. Portable Python script across version

    Have all classes derive from object: that's implicitly the default in Python3,
    it needs to be done explicilty in Python2.

    Differential Revision: https://reviews.llvm.org/D55121 (detail)
    by serge_sans_paille
  2. Portable Python script across Python version

    Python2 supports the two following equivalent construct

    raise ExceptionType, exception_value
    and
    raise ExceptionType(exception_value)

    Only the later is supported by Python3.

    Differential Revision: https://reviews.llvm.org/D55195 (detail)
    by serge_sans_paille
  3. [Analyzer] Actually check for -model-path being a directory

    The original patch (r348038) clearly contained a typo and checked
    for '-ctu-dir' twice. (detail)
    by ibiryukov
  4. [Analysis] Properly prepare test env in test/Analysis/undef-call.c

    The test expectes the '%T/ctudir' to be present, but does not create it. (detail)
    by ibiryukov
  5. [clang] Do not read from 'test/SemaCXX/Inputs' inside 'test/AST'

    Our integrate relies on test inputs being taken from the same diretory as the
    test itself. (detail)
    by ibiryukov
  6. ARM: use target-specific SUBS node when combining cmp with cmov.

    This has two positive effects. First, using a custom node prevents
    recombination leading to an infinite loop since the output DAG is notionally a
    little more complex than the input one. Using a flag-setting instruction also
    allows the subtraction to be folded with the related comparison more easily.

    https://reviews.llvm.org/D53190 (detail)
    by Tim Northover
  7. [NFC][AArch64] Split out backend features

    This patch splits backend features currently
    hidden behind architecture versions.

    For example, currently the only way to activate
    complex numbers extension is targeting an v8.3
    architecture, where after the patch this extension
    can be added separately.

    This refactoring is required by the new command lines proposal:
    http://lists.llvm.org/pipermail/llvm-dev/2018-September/126346.html

    Reviewers: DavidSpickett, olista01, t.p.northover

    Subscribers: kristof.beyls, bryanpkc, javed.absar, pbarrio

    Differential revision: https://reviews.llvm.org/D54633 (detail)
    by dnsampaio
  8. [OpenCL][Sema] Improve BuildResolvedCallExpr handling of builtins

    Summary:
    This is a follow-up on https://reviews.llvm.org/D52879, addressing a few issues.

    This:
    - adds a FIXME for later improvement for specific builtins: I previously have only checked OpenCL ones and ensured tests cover those.
    - fixed the CallExpr type.



    Reviewers: riccibruno

    Reviewed By: riccibruno

    Subscribers: yaxunl, Anastasia, kristina, svenvh, cfe-commits

    Differential Revision: https://reviews.llvm.org/D55136 (detail)
    by mantognini
  9. [CMake] Add LLVM_EXTERNALIZE_DEBUGINFO_OUTPUT_DIR for custom dSYM target directory on Darwin

    Summary: When using `LLVM_EXTERNALIZE_DEBUGINFO` in LLDB, the default dSYM location for the shared library in LLDB.framework is inside the framework bundle. With `LLVM_EXTERNALIZE_DEBUGINFO_OUTPUT_DIR` we can easily fix that. I consider it a useful feature to be able to set a global output directory for external debug info (rather then having a target-specific one). Only implemented for Darwin so far.

    Reviewers: beanz, aprantl

    Reviewed By: aprantl

    Subscribers: mgorny, aprantl, #lldb, lldb-commits, llvm-commits

    Differential Revision: https://reviews.llvm.org/D55114 (detail)
    by stefan.graenitz
  10. [RISCV] Fix test/MC/Disassembler/RISCV/invalid-instruction.txt after rL347988

    The test for [0x00 0x00] failed due to the introduction of c.unimp.

    This particular test is unnecessary now that c.unimp was defined (and is
    tested in test/MC/RISCV/rv32c-valid.s). (detail)
    by asb
  11. [CMake] Store path to vendor-specific headers in clang-headers target property

    Summary:
    LLDB.framework wants a copy these headers. With this change LLDB can easily glob for the list of files:
    ```
    get_target_property(clang_include_dir clang-headers RUNTIME_OUTPUT_DIRECTORY)
    file(GLOB_RECURSE clang_vendor_headers RELATIVE ${clang_include_dir} "${clang_include_dir}/*")
    ```

    By default `RUNTIME_OUTPUT_DIRECTORY` is unset for custom targets like `clang-headers`.

    Reviewers: aprantl, JDevlieghere, davide, friss, dexonsmith

    Reviewed By: JDevlieghere

    Subscribers: mgorny, #lldb, cfe-commits, llvm-commits

    Differential Revision: https://reviews.llvm.org/D55128 (detail)
    by stefan.graenitz
  12. [llvm-dwarfdump] - Stop printing the bogus empty section name on invalid dwarf.

    When there is no .debug_addr section for some reason,
    llvm-dwarfdump would print the bogus empty section name when dumping ranges
    in .debug_info:

    DW_AT_ranges [DW_FORM_rnglistx]   (indexed (0x0) rangelist = 0x00000004
        [0x0000000000000000, 0x0000000000000001) ""
        [0x0000000000000000, 0x0000000000000002) "")

    That happens because of the code which uses 0 (zero) as a section index as a default value.
    The code should use -1ULL instead because technically 0 is a valid zero section index
    in ELF and -1ULL is a special constant used that means "no section available".

    This is mostly a fix for the overall correctness/safety of the code,
    but a test case is provided too.

    Differential revision: https://reviews.llvm.org/D55113 (detail)
    by grimar
  13. [ARM][MC] Move information about variadic register defs into tablegen

    Currently, variadic operands on an MCInst are assumed to be uses,
    because they come after the defs. However, this is not always the case,
    for example the Arm/Thumb LDM instructions write to a variable number of
    registers.

    This adds a property of instruction definitions which can be used to
    mark variadic operands as defs. This only affects MCInst, because
    MachineInstruction already tracks use/def per operand in each instance
    of the instruction, so can already represent this.

    This property can then be checked in MCInstrDesc, allowing us to remove
    some special cases in ARMAsmParser::isITBlockTerminator.

    Differential revision: https://reviews.llvm.org/D54853 (detail)
    by olista01
  14. [ARM][Asm] Debug trace for the processInstruction loop

    In the Arm assembly parser, we first match an instruction, then call
    processInstruction to possibly change it to a different encoding, to
    match rules in the architecture manual which can't be expressed by the
    table-generated matcher.

    This adds debug printing so that this process is visible when using the
    -debug option.

    To support this, I've added a new overload of MCInst::dump_pretty which
    takes the opcode name as a StringRef, since we don't have an InstPrinter
    instance in the assembly parser. Instead, we can get the same
    information directly from the MCInstrInfo.

    Differential revision: https://reviews.llvm.org/D54852 (detail)
    by olista01
  15. [KMSAN] Enable -msan-handle-asm-conservative by default

    This change enables conservative assembly instrumentation in KMSAN builds
    by default.
    It's still possible to disable it with -msan-handle-asm-conservative=0
    if something breaks. It's now impossible to enable conservative
    instrumentation for userspace builds, but it's not used anyway. (detail)
    by glider

Started by timer (10 times)

This run spent:

  • 2 hr 27 min waiting;
  • 28 min build duration;
  • 2 hr 55 min total from scheduled to completion.
Test Result (675 failures / ±0)Show all failed tests >>>

Identified problems

Regression test failed

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

Ninja target failed

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