Started 9 days 20 hr ago
Took 5 hr 14 min on green-dragon-02

Failed Build #14690 (Sep 13, 2019 12:43:30 PM)

  • : 371888
  • : 371878
  • : 371872
  • : 371835
  • : 371886
  • : 371773
  1. [FPEnv] Document that constrained FP intrinsics cannot be mixed with non-constrained

    Reviewed by: andrew.w.kaylor, cameron.mcinally, uweigand
    Approved by: andrew.w.kaylor
    Differential Revision: (detail)
    by kpn
  2. [aarch64] move custom isel of extract_vector_elt to td file - NFC

    In preparation for def-pat selection of dot product instructions,
    this patch moves the custom instruction selection of extract_vector_elt
    to the td file. Without this change it is impossible to catch a pattern that
    starts with an extract_vector_elt: the custom cpp code is executed first
    ahead of the patterns in the td files that are only executed at the end of
    the switch statement in SelectCode(Node).

    With this patch applied, it becomes possible to select a different pattern
    that starts with extract_vector_elt by selecting a higher complexity than
    this pattern.

    The patch has been tested on aarch64-linux with make check-all.

    Differential Revision: (detail)
    by spop
  3. Mark [[nodiscard]] test as unsupported with GCC 5 (detail)
    by ericwf
  4. Fix pretty printer test with GCC (detail)
    by ericwf
  5. AArch64: fix EXPENSIVE_CHECKS for arm64_32.

    For some reason I'd decided to mark the end-result of a GOT load as
    dead. It's clearly not (necessarily). (detail)
    by Tim Northover
  6. Fix various test failures with GCC (detail)
    by ericwf
  7. [SLP] add test for vectorization of constant expressions; NFC

    Goes with D67362. (detail)
    by spatel
  8. Reland r371785: Add -Wpoison-system-directories warning

    When using clang as a cross-compiler, we should not use system
    headers to do the compilation.
    This CL adds support of a new warning flag -Wpoison-system-directories which
    emits warnings if --sysroot is set and headers from common host system location
    are used.
    By default the warning is disabled.

    The intention of the warning is to catch bad includes which are usually
    generated by third party build system not targeting cross-compilation.
    Such cases happen in Chrome OS when someone imports a new package or upgrade
    one to a newer version from upstream.

    This is reland of r371785 with a fix to test file.

    Patch by: denik (Denis Nikitin) (detail)
    by manojgupta
  9. [NFC][InstSimplify] Add some more tests for D67498/D67502 (detail)
    by lebedevri
  10. Fix build error in 371875

    Apparently Clang complains about the name hiding here in a way that my
    GCC build does not, so a shocking number of buildbots decided to tell me
    about it.  Change the name of the variable to prevent the name hiding
    and hope we don't have to fix this again. (detail)
    by erichkeane
  11. [NFCI]Create CommonAttributeInfo Type as base type of *Attr and ParsedAttr.

    In order to enable future improvements to our attribute diagnostics,
    this moves info from ParsedAttr into CommonAttributeInfo, then makes
    this type the base of the *Attr and ParsedAttr types. Quite a bit of
    refactoring took place, including removing a bunch of redundant Spelling
    Index propogation.

    Differential Revision: (detail)
    by erichkeane
  12. Fix failing negative compilation test for some versions of Clang (detail)
    by ericwf
  13. Revert for: [AMDGPU]: PHI Elimination hooks added for custom COPY insertion. (detail)
    by alex-t
  14. Fix bug in `darwin_test_archs()` when the cache variable is set but empty.

    If the cache variable named in `${valid_archs}` (e.g. `DARWIN_osx_BUILTIN_ARCHS`)
    is set in the cache but is empty then the cache check
    `if(${valid_archs})` will be false so the function will probe the
    compiler but the `set(...)` command at the end of the function to update
    the cache variable will be a no-op. This is because `set(...)` will not
    update an existing cache variable unless the `FORCE` argument is

    To fix this this patch adds `FORCE` so the cache is always updated.


    Reviewers: vsk, kubamracek

    Subscribers: mgorny, #sanitizers, llvm-commits

    Tags: #llvm, #sanitizers

    Differential Revision: (detail)
    by delcypher
  15. [CMake] Separate the detection Darwin platforms architectures for the
    built-ins from the rest of compiler-rt.

    The detection of supported platform (os) architectures for Darwin relies
    on the `darwin_test_archs()` CMake function. This is used both for
    building the builtins (`builtin-config-ix.cmake`) and for the rest of
    the compiler-rt (`config-ix.cmake`).

    `darwin_test_archs()`  implements a cache, presumably to speed up CMake
    re-configures.  Unfortunately this caching is buggy because it depends
    on external global state (i.e. the `TEST_COMPILE_ONLY` variable) and
    this is not taken into account. For `config-ix.cmake`
    `TEST_COMPILE_ONLY` is not set and for `builtin-config-ix.cmake`
    `TEST_COMPILE_ONLY` is set to `On`.  This makes the
    `darwin_test_archs()` function racey in the sense that a call from one
    calling context will poison the cache for the other calling context.

    This is actually an issue George Karpenkov discovered a while back
    and had an incomplete patch for (
    but this was never merged.

    To workaround this, this patch switches to using a different set of
    variables for the platform architecture builtins, i.e.
    `DARWIN_<OS>_ARCHS` -> `DARWIN_<OS>_BUILTIN_ARCHS`. This avoids the
    cache poisoning problem because the cached variable names are different.
    This also has the advantage that the the configured architectures for
    builtins and the rest of the compiler-rt are now independent and
    can be set differently if necessary.

    Note in `darwin_test_archs()` we also now pass `-w` to the compiler
    because `try_compile_only()` treats compiler warnings as errors.  This
    was extremely fragile because compiler warnings (can easily appear due
    to a buggy compiler or SDK headers) would cause compiler-rt to think an
    architecture on Darwin wasn't supported.

    rdar://problem/48637491 (detail)
    by delcypher
  16. [Remarks][NFC] Forward declare ParsedStringTable (detail)
    by thegameg
  17. [Remarks][NFC] Use StringLiteral for magic numbers (detail)
    by thegameg
  18. [AArch64][GlobalISel] Add support for sibcalling callees with varargs

    This adds support for tail calling callees with varargs, equivalent to how it
    is done in AArch64ISelLowering.

    This only works for sibling calls, and does not add the necessary support for
    musttail with varargs. (See r345641 for equivalent ISelLowering support.) This
    should be implemented when we stop falling back on musttail.

    Update call-translator-tail-call.ll to show that we can now tail call varargs.

    Differential Revision: (detail)
    by paquette
  19. Recommit r370502: Make `vector` unconditionally move elements when
    exceptions are disabled.

    The patch was reverted due to some confusion about non-movable types. ie
    that explicitly delete their move constructors. However, such types do
    not meet
    the requirement for `MoveConstructible`, which is required by


    `std::vector<T>` is free choose between using copy or move operations
    when it
    needs to resize. The standard only candidates that the correct exception
    guarantees are provided. When exceptions are disabled these guarantees
    trivially satisfied. Meaning vector is free to optimize it's
    implementation by
    moving instead of copying.

    This patch makes `std::vector` unconditionally move elements when
    exceptions are
    disabled. This optimization is conforming according to the current
    standard wording.

    There are concerns that moving in `-fno-noexceptions`mode will be a
    surprise to
    users. For example, a user may be surprised to find their code is slower
    exceptions enabled than it is disabled. I'm sympathetic to this
    surprised, but
    I don't think it should block this optimization.

    Reviewers: mclow.lists, ldionne, rsmith
    Reviewed By: ldionne
    Subscribers: zoecarver, christof, dexonsmith, libcxx-commits
    Tags: #libc
    Differential Revision: (detail)
    by ericwf
  20. [yaml2obj/ObjectYAML] - Cleanup the error reporting API, add custom errors handlers.

    This is a continuation of the YAML library error reporting
    refactoring/improvement and the idea by itself was mentioned
    in the following thread:

    This performs a cleanup of all object emitters in the library.
    It allows using the custom one provided by the caller.

    One of the nice things is that each tool can now print its tool name,
    e.g: "yaml2obj: error: <text>"

    Also, the code became a bit simpler.

    Differential revision: (detail)
    by grimar

Started by timer (4 times)

This run spent:

  • 3 hr 32 min waiting;
  • 5 hr 14 min build duration;
  • 8 hr 46 min total from scheduled to completion.
Test Result (2 failures / -3)

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

Compile Error

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