Started 1 mo 3 days ago
Took 1 hr 32 min on green-dragon-22

Success Build rL:372384 - C:372387 - #691 (Sep 20, 2019 6:10:02 AM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 372384
  • http://llvm.org/svn/llvm-project/cfe/trunk : 372387
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 372348
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 364589
  • http://llvm.org/svn/llvm-project/zorg/trunk : 372342
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 372242
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 372388
Changes
  1. [clang-tidy] Fix relative path in header-filter.

    Summary:
    Clang-tidy supports output diagnostics from header files if user
    specifies --header-filter. But it can't handle relative path well.
    For example, the folder structure of a project is:

    ```
    // a.h is in /src/a/a.h

    // b.h is in /src/b/b.h
    ...

    // c.cpp is in /src/c.cpp

    ```

    Now, we set --header-filter as --header-filter=/a/. That means we only
    want to check header files under /src/a/ path, and ignore header files
    uder /src/b/ path, but in current implementation, clang-tidy will check
    /src/b/b.h also, because the name of b.h used in clang-tidy is
    /src/a/../b/b.h.

    This change tries to fix this issue.

    Reviewers: alexfh, hokein, aaron.ballman, gribozavr

    Reviewed By: gribozavr

    Subscribers: MyDeveloperDay, xazax.hun, cfe-commits

    Tags: #clang, #clang-tools-extra

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

    Patch by Yubo Xie. (detail/ViewSVN)
    by gribozavr
  2. [SystemZ]  Add SystemZ as supporting target in help text for -mfentry.

    => "Insert calls to fentry at function entry (x86/SystemZ only)"

    Review: Ulrich Weigand (detail/ViewSVN)
    by jonpa
  3. [StaticAnalyzer] Use llvm::StringLiteral instead of StringRef in few places

    StringRef's constexpr constructor seems to be extremely slow in MSVC
    2017, so don't use it for generated tables. Should make PR43369 a bit
    better, no functionality change. (detail/ViewSVN)
    by d0k
  4. [AMDGPU] Use std::make_tuple to make some toolchains happy again

    My toolchain stopped working (LLVM 8.0 , libstdc++ 5.4.0) after
    r372338.

    The same problem was seen in clang-cuda-build buildbots:

    clang-cuda-build/llvm/lib/Target/AMDGPU/AMDGPUInstructionSelector.cpp:763:12:
    error: chosen constructor is explicit in copy-initialization
        return {Reg, 0, nullptr};
               ^~~~~~~~~~~~~~~~~
    /usr/bin/../lib/gcc/x86_64-linux-gnu/5.4.0/../../../../include/c++/5.4.0/tuple:479:19:
    note: explicit constructor declared here
            constexpr tuple(_UElements&&... __elements)
                      ^

    This commit adds explicit calls to std::make_tuple to work around
    the problem. (detail/ViewSVN)
    by bjope
  5. Revert r372366 "Use getTargetConstant for BLENDI, and add a test to catch it."

    This reverts commit 52621307bcab2013e8833f3317cebd63a6db3885.

    Tests have been failing all night with

        [0/2] ACTION //llvm/test:check-llvm(//llvm/utils/gn/build/toolchain:unix)
        -- Testing: 33647 tests, 64 threads --
        Testing: 0 .. 10..
        UNRESOLVED: LLVM :: CodeGen/AMDGPU/GlobalISel/isel-blendi-gettargetconstant.ll (6943 of 33647)
        ******************** TEST 'LLVM :: CodeGen/AMDGPU/GlobalISel/isel-blendi-gettargetconstant.ll' FAILED ********************
        Test has no run line!
        ********************

    Since there were other concerns on https://reviews.llvm.org/D67785,
    I'm just reverting for now. (detail/ViewSVN)
    by nico

Started by an SCM change (3 times)

This run spent:

  • 1 hr 3 min waiting;
  • 1 hr 32 min build duration;
  • 2 hr 35 min total from scheduled to completion.
LLVM/Clang Warnings: 1 warning.
    Test Result (no failures)