Started 12 days ago
Took 5 hr 10 min on green-dragon-02

Failed Build #14362 (Jul 9, 2019 6:54:40 AM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 365477
  • http://llvm.org/svn/llvm-project/cfe/trunk : 365480
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 365424
  • http://llvm.org/svn/llvm-project/zorg/trunk : 365440
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 365359
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 365463
Changes
  1. [ItaniumMangle] Refactor long double/__float128 mangling and fix the mangled code

    In gcc PowerPC, long double has 3 mangling schemes:

    -mlong-double-64: `e`
    -mlong-double-128 -mabi=ibmlongdouble: `g`
    -mlong-double-128 -mabi=ieeelongdouble: `u9__ieee128` (gcc <= 8.1: `U10__float128`)

    The current useFloat128ManglingForLongDouble() bisection is not suitable
    when we support -mlong-double-128 in clang (D64277). Replace
    useFloat128ManglingForLongDouble() with getLongDoubleMangling() and
    getFloat128Mangling() to allow 3 mangling schemes.

    I also deleted the `getTriple().isOSBinFormatELF()` check (the Darwin
    support has gone: https://reviews.llvm.org/D50988).

    For x86, change the mangled code of __float128 from `U10__float128` to `g`. `U10__float128` was wrongly copied from PowerPC.
    The test will be added to `test/CodeGen/x86-long-double.cpp` in D64277.

    Reviewed By: erichkeane

    Differential Revision: https://reviews.llvm.org/D64276 (detail)
    by maskray
  2. [Syntax] Move roles into a separate enum

    To align with reviewer's suggestions. (detail)
    by ibiryukov
  3. [CodeGen] AccelTable - remove non-constexpr (MSVC) Atom defs

    Now that we've dropped VS2015 support (D64326) we can enable the constexpr variables on MSVC builds as VS2017+ correctly handles them (detail)
    by rksimon
  4. [mips] Implement sge/sgeu pseudo instructions

    The `sge/sgeu Dst, Src1, Src2/Imm` pseudo instructions set register
    `Dst` to 1 if register `Src1` is greater than or equal `Src2/Imm` and
    to 0 otherwise.

    Differential Revision: https://reviews.llvm.org/D64314 (detail)
    by atanasyan
  5. [mips] Implement sgt/sgtu pseudo instructions with immediate operand

    The `sgt/sgtu Dst, Src1, Src2/Imm` pseudo instructions set register
    `Dst` to 1 if register `Src1` is greater than `Src2/Imm` and to 0 otherwise.

    Differential Revision: https://reviews.llvm.org/D64313 (detail)
    by atanasyan
  6. [docs][llvm-objdump] Make some wording improvements/simplifications. (detail)
    by jhenderson
  7. [NFC] [X86] Fix scan-build complaining

    Summary:
    Remove unused variable. This fixes bug:
    https://bugs.llvm.org/show_bug.cgi?id=42526

    Signed-off-by: pengfei <pengfei.wang@intel.com>

    Reviewers: RKSimon, xiangzhangllvm, craig.topper

    Subscribers: cfe-commits

    Tags: #clang

    Differential Revision: https://reviews.llvm.org/D64389 (detail)
    by pengfei
  8. OpaquePtr: pass type to CreateLoad. NFC.

    This is the one place in LLVM itself that used the deprecated API for
    CreateLoad, so I just added the type in. (detail)
    by Tim Northover
  9. [ADT] Enable ArrayRef/StringRef is_assignable tests on MSVC

    Now that we've dropped VS2015 support (D64326) we can enable these static_asserts on MSVC builds as VS2017+ correctly handles them (detail)
    by rksimon
  10. [NFC][AsmPrinter] Fix the formatting for the rL365467

    In addition, fix the build failure for the 'unused'
    variable. The variable was used inside the 'LLVM_DEBUG()'. (detail)
    by djtodoro
  11. OpaquePtr: add Type parameter to Loads analysis API.

    This makes the functions in Loads.h require a type to be specified
    independently of the pointer Value so that when pointers have no structure
    other than address-space, it can still do its job.

    Most callers had an obvious memory operation handy to provide this type, but a
    SROA and ArgumentPromotion were doing more complicated analysis. They get
    updated to merge the properties of the various instructions they were
    considering. (detail)
    by Tim Northover
  12. [DwarfDebug] Dump call site debug info

    Dump the DWARF information about call sites and call site parameters into
    debug info sections.

    The patch also provides an interface for the interpretation of instructions
    that could load values of a call site parameters in order to generate DWARF
    about the call site parameters.

    ([13/13] Introduce the debug entry values.)

    Co-authored-by: Ananth Sowda <asowda@cisco.com>
    Co-authored-by: Nikola Prica <nikola.prica@rt-rk.com>
    Co-authored-by: Ivan Baev <ibaev@cisco.com>

    Differential Revision: https://reviews.llvm.org/D60716 (detail)
    by djtodoro
  13. Reland r365355: [Syntax] Introduce syntax trees

    With a fix to a PS4 buildbot crash. (detail)
    by ibiryukov
  14. Revert rL365355 : [Syntax] Introduce syntax trees

    Summary:
    A tooling-focused alternative to the AST. This commit focuses on the
    memory-management strategy and the structure of the AST.

    More to follow later:
      - Operations to mutate the syntax trees and corresponding textual
        replacements.
      - Mapping between clang AST nodes and syntax tree nodes.
      - More node types corresponding to the language constructs.

    Reviewers: sammccall

    Reviewed By: sammccall

    Subscribers: llvm-commits, mgorny, cfe-commits

    Tags: #clang, #llvm

    Differential Revision: https://reviews.llvm.org/D61637
    ........
    Fixes buildbots which were crashing on SyntaxTests.exe (detail)
    by rksimon
  15. [ASTImporter] Added visibility context check for EnumDecl.

    Summary:
    ASTImporter makes now difference between enums with same name in different translation
    units if these are not visible outside.
    ("Scoped enums" are not handled yet.)

    Reviewers: martong, a.sidorin, shafik, a_sidorin

    Reviewed By: a_sidorin

    Subscribers: rnkovacs, dkrupp, Szelethus, gamesh411, cfe-commits

    Tags: #clang

    Differential Revision: https://reviews.llvm.org/D62484 (detail)
    by balazske
  16. Enhance abseil-faster-strsplit-delimiter to handle other non-printable characters.

    Summary:
    Currently it fails on cases like '\001'.

    Note: Since `StringLiteral::outputString` dumps most nonprintable
    characters in octal value, the exact string literal format isn't preserved,
    e.g. `"\x01"` becomes `'\001'`.

    Reviewers: gribozavr

    Reviewed By: gribozavr

    Subscribers: lebedev.ri, Eugene.Zelenko, cfe-commits

    Tags: #clang

    Differential Revision: https://reviews.llvm.org/D64151

    Patch by Xiaoyi Zhang. (detail)
    by gribozavr
  17. [RISCV] Fix RISCVTTIImpl::getIntImmCost for immediates where getMinSignedBits() > 64

    APInt::getSExtValue will assert if getMinSignedBits() > 64. This can happen,
    for instance, if examining an i128. Avoid this assertion by checking
    Imm.getMinSignedBits() <= 64 before doing
    getTLI()->isLegalAddImmediate(Imm.getSExtValue()). We could directly check
    getMinSignedBits() <= 12 but it seems better to reuse the isLegalAddImmediate
    helper for this.

    Differential Revision: https://reviews.llvm.org/D64390 (detail)
    by asb
  18. [docs][llvm-nm] Improve some wording

    In particular, the --debug-syms switch really doesn't have anything to
    do with debuggers, so I've updated the document accordingly. (detail)
    by jhenderson
  19. Fixed assertion (detail)
    by sureyeaah
  20. [SelectionDAG] Simplify some calls to getSetCCResultType. NFC

    DAGTypeLegalizer and SelectionDAGLegalize has helper
    functions wrapping the call to TLI.getSetCCResultType(...).
    Use those helpers in more places. (detail)
    by bjope
  21. [LegalizeTypes] Fix saturation bug for smul.fix.sat

    Summary:
    Make sure we use SETGE instead of SETGT when checking
    if the sign bit is zero at SMULFIXSAT expansion.

    The faulty expansion occured when doing "expand" of
    SMULFIXSAT and the scale was exactly matching the
    size of the smaller type. For example doing
      i64 Z = SMULFIXSAT X, Y, 32
    and expanding X/Y/Z into using two i32 values.

    The problem was that we sometimes did not saturate
    to min when overflowing.

    Here is an example using Q3.4 numbers:

    Consider that we are multiplying X and Y.
      X = 0x80 (-8.0 as Q3.4)
      Y = 0x20 (2.0 as Q3.4)
    To avoid loss of precision we do a widening
    multiplication, getting a 16 bit result
      Z = 0xF000 (-16.0 as Q7.8)

    To detect negative overflow we should check if
    the five most significant bits in Z are less than -1.
    Assume that we name the 4 most significant bits
    as HH and the next 4 bits as HL. Then we can do the
    check by examining if
    (HH < -1) or (HH == -1 && "sign bit in HL is zero").

    The fault was that we have been doing the check as
    (HH < -1) or (HH == -1 && HL > 0)
    instead of
    (HH < -1) or (HH == -1 && HL >= 0).

    In our example HH is -1 and HL is 0, so the old
    code did not trigger saturation and simply truncated
    the result to 0x00 (0.0). With the bugfix we instead
    detect that we should saturate to min, and the result
    will be set to 0x80 (-8.0).

    Reviewers: leonardchan, bevinh

    Reviewed By: leonardchan

    Subscribers: hiraditya, llvm-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D64331 (detail)
    by bjope
  22. Retire VS2015 Support

    As proposed here: https://lists.llvm.org/pipermail/llvm-dev/2019-June/133147.html

    This patch raises the minimum supported version to build LLVM/Clang to Visual Studio 2017.

    Differential Revision: https://reviews.llvm.org/D64326 (detail)
    by rksimon
  23. dummy variable extraction on a function scope

    Summary:
    - Added extraction to a dummy variable
    - using auto for the dummy variable type for now
    - Works on a function scope
    - Adding braces to create a compound statement not supported yet
    - added unit tests

    Reviewers: sammccall, kadircet

    Subscribers: mgorny, jkorous, arphaman, cfe-commits

    Tags: #clang

    Differential Revision: https://reviews.llvm.org/D63773 (detail)
    by sureyeaah
  24. Retire VS2015 Support

    As proposed here: https://lists.llvm.org/pipermail/llvm-dev/2019-June/133147.html

    This patch raises the minimum supported version to build LLVM/Clang to Visual Studio 2017.

    Differential Revision: https://reviews.llvm.org/D64326 (detail)
    by rksimon
  25. [docs][llvm-dwarfdump] Make some option descriptions clearer and more precise

    Some of the wording in the doc (taken largely from the help text), was a
    little imprecise in some cases, so this patch makes it a little more
    precise.

    Reviewed by: JDevlieghere, probinson

    Differential Revision: https://reviews.llvm.org/D64332 (detail)
    by jhenderson
  26. [llvm-profdata] Don't make the output overwrite the input file.

    Some file systems may not allow this behavior, the test fails on our internal
    system ("Permission denied"). (detail)
    by hokein
  27. Fixing @llvm.memcpy not honoring volatile.
    This is explicitly not addressing target-specific code, or calls to memcpy.

    Summary: https://bugs.llvm.org/show_bug.cgi?id=42254

    Reviewers: courbet

    Subscribers: hiraditya, llvm-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D63215 (detail)
    by gchatelet
  28. Revert r364515 and r364524

    Jordan reports on llvm-commits a performance regression with r364515,
    backing the patch out while it's investigated. (detail)
    by jmorse
  29. [NFC][PowerPC] Added a test to show current codegen of MachinePRE (detail)
    by lkail

Started by timer (5 times)

This run spent:

  • 4 hr 43 min waiting;
  • 5 hr 10 min build duration;
  • 9 hr 54 min total from scheduled to completion.
Test Result (5 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

Unexpected pass

This buildbot failed because a test marked as XFAIL unexpectedly passes. This could mean that the cause for the XFAIL is fixed, but it warrants investigation in any case.
Indication 2