Started 15 days ago
Took 1 hr 21 min on green-dragon-09

Success Build #17888 (Jul 8, 2019 7:22:22 AM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 365320
  • http://llvm.org/svn/llvm-project/cfe/trunk : 365315
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 365307
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 364589
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 365290
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 365311
Changes
  1. GlobalISel: widenScalar for G_BUILD_VECTOR (detail/ViewSVN)
    by arsenm
  2. GlobalISel: Check address space when looking up iPTR size

    Fixes AMDGPU patterns for 32-bit address spaces always failing. Tests
    will be included in future patches when additional issues are solved. (detail/ViewSVN)
    by arsenm
  3. Reapply [llvm-ar][test] Increase llvm-ar test coverage

    This change adds tests to cover existing llvm-ar functionality.

    Differential Revision: https://reviews.llvm.org/D63935 (detail/ViewSVN)
    by gbreynoo
  4. Revert [llvm-ar][test] Increase llvm-ar test coverage

    Reverted due to test failures

    Differential Revision: https://reviews.llvm.org/D63935 (detail/ViewSVN)
    by gbreynoo
  5. [llvm-ar][test] Increase llvm-ar test coverage

    This change adds tests to cover existing llvm-ar functionality.

    Differential Revision: https://reviews.llvm.org/D63935 (detail/ViewSVN)
    by gbreynoo
  6. [ASTImporter] Fix import of lambda in function param

    Summary:
    The current import implementation fails to import the definition of a
    lambda class if the lambda class is defined in a function param.
    E.g., the lambda class below will be imported without any methods:
    ```
      template <typename F>
      void f(F L = [](){}) {}
    ```

    Reviewers: a_sidorin, a.sidorin, shafik

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

    Tags: #clang

    Differential Revision: https://reviews.llvm.org/D64073 (detail/ViewSVN)
    by martong
  7. [analyzer] Add analyzer option to limit the number of imported TUs

    Summary:
    During CTU analysis of complex projects, the loaded AST-contents of
    imported TUs can grow bigger than available system memory. This option
    introduces a threshold on the number of TUs to be imported for a single
    TU in order to prevent such cases.

    Differential Revision: https://reviews.llvm.org/D59798 (detail/ViewSVN)
    by gamesh411
  8. [lit] Parse command-line options from LIT_OPTS

    Similar to `FILECHECK_OPTS` for FileCheck, `LIT_OPTS` makes it easy to
    adjust lit behavior when running the test suite via ninja.  For
    example:

    ```
    $ LIT_OPTS='--time-tests -vv --filter=threadprivate' \
      ninja check-clang-openmp
    ```

    Reviewed By: probinson

    Differential Revision: https://reviews.llvm.org/D64135 (detail/ViewSVN)
    by jdenny
  9. [docs][llvm-objcopy] Add description of binary input/output to doc

    We briefly referred to being able to specify --target=binary without
    explaining what binary input/output meant. This change adds a section on
    this.

    Reviewed by: MaskRay, abrachet

    Differential Revision: https://reviews.llvm.org/D64245 (detail/ViewSVN)
    by jhenderson
  10. [TargetLowering] SimplifyDemandedBits - just call computeKnownBits for BUILD_VECTOR cases.

    Don't do this locally, computeKnownBits does this better (and can handle non-constant cases as well).

    A next step would be to actually simplify non-constant elements - building on what we already do in SimplifyDemandedVectorElts. (detail/ViewSVN)
    by rksimon

Started by upstream project SVN: Clang Stage 1: cmake, RA, using system compiler build number 57790
originally caused by:

This run spent:

  • 10 min waiting;
  • 1 hr 21 min build duration;
  • 1 hr 32 min total from scheduled to completion.
LLVM/Clang Warnings: 0 warnings.
  • No warnings since build 17,881.
  • Still 69 days before reaching the previous zero warnings highscore.