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

Failed Build #14671 (Sep 11, 2019 7:49:31 AM)

  • : 371626
  • : 371627
  • : 371628
  • : 371613
  • : 371324
  • : 371504
  1. [scudo][standalone] Android related improvements

    This changes a few things to improve memory footprint and performances
    on Android, and fixes a test compilation error:
    - add `stdlib.h` to `` to address
    - change Android size class maps, based on benchmarks, to improve
      performances and lower the Svelte memory footprint. Also change the
      32-bit region size for said configuration
    - change the `reallocate` logic to reallocate in place for sizes larger
      than the original chunk size, when they still fit in the same block.
      This addresses patterns from `memory_replay` dumps like the following:
    202: realloc 0xb48fd000 0xb4930650 12352
    202: realloc 0xb48fd000 0xb48fd000 12420
    202: realloc 0xb48fd000 0xb48fd000 12492
    202: realloc 0xb48fd000 0xb48fd000 12564
    202: realloc 0xb48fd000 0xb48fd000 12636
    202: realloc 0xb48fd000 0xb48fd000 12708
    202: realloc 0xb48fd000 0xb48fd000 12780
    202: realloc 0xb48fd000 0xb48fd000 12852
    202: realloc 0xb48fd000 0xb48fd000 12924
    202: realloc 0xb48fd000 0xb48fd000 12996
    202: realloc 0xb48fd000 0xb48fd000 13068
    202: realloc 0xb48fd000 0xb48fd000 13140
    202: realloc 0xb48fd000 0xb48fd000 13212
    202: realloc 0xb48fd000 0xb48fd000 13284
    202: realloc 0xb48fd000 0xb48fd000 13356
    202: realloc 0xb48fd000 0xb48fd000 13428
    202: realloc 0xb48fd000 0xb48fd000 13500
    202: realloc 0xb48fd000 0xb48fd000 13572
    202: realloc 0xb48fd000 0xb48fd000 13644
    202: realloc 0xb48fd000 0xb48fd000 13716
    202: realloc 0xb48fd000 0xb48fd000 13788
      In this situation we were deallocating the old chunk, and
      allocating a new one for every single one of those, but now we can
      keep the same chunk (we just updated the header), which saves some
      heap operations.

    Reviewers: hctim, morehouse, vitalybuka, eugenis, cferris, rengolin

    Reviewed By: morehouse

    Subscribers: srhines, delcypher, #sanitizers, llvm-commits

    Tags: #llvm, #sanitizers

    Differential Revision: (detail)
    by cryptoad
  2. [OPENMP]Updated status page, NFC. (detail)
    by abataev
  3. gn build: Merge r371562 (detail)
    by nico
  4. LLVM: Optimization Pass: Remove conflicting attribute, if any, before
    adding new read attribute to an argument
    Summary: Update optimization pass to prevent adding read-attribute to an
    argument without removing its conflicting attribute.

    A read attribute, based on the result of the attribute deduction
    process, might be added to an argument. The attribute might be in
    conflict with other read/write attribute currently associated with the
    argument. To ensure the compatibility of attributes, conflicting
    attribute, if any, must be removed before a new one is added.

    The following snippet shows the current behavior of the compiler, where
    the compilation process is aborted due to incompatible attributes.

    $ cat x.ll
    ; ModuleID = 'x.bc'

    %_type_of_d-ccc = type <{ i8*, i8, i8, i8, i8 }>

    @d-ccc = internal global %_type_of_d-ccc <{ i8* null, i8 1, i8 13, i8 0,
    i8 -127 }>, align 8

    define void @foo(i32* writeonly {
    foo_entry: = alloca i32*, align 8
      store i32*, i32**, align 8
      store i8 0, i8* getelementptr inbounds (%_type_of_d-ccc,
    %_type_of_d-ccc* @d-ccc, i32 0, i32 3)
      ret void

    $ opt -O3 x.ll
    Attributes 'readnone and writeonly' are incompatible!
    void (i32*)* @foo
    in function foo
    LLVM ERROR: Broken function found, compilation aborted!
    The purpose of this changeset is to fix the above error. This fix is
    based on a suggestion from Johannes @jdoerfert (many thanks!!!)
    Authored By: anhtuyen
    Reviewer: nicholas, rnk, chandlerc, jdoerfert
    Reviewed By: rnk
    Subscribers: hiraditya, jdoerfert, llvm-commits, anhtuyen, LLVM
    Tag: LLVM
    Differential Revision: (detail)
    by whitneyt
  5. [ConstProp] add tests for fma that produce NaN; NFC (detail)
    by spatel
  6. [libFuzzer] Make -merge=1 to reuse coverage information from the control file.

    This change allows to perform corpus merging in two steps. This is useful when
    the user wants to address the following two points simultaneously:

    1) Get trustworthy incremental stats for the coverage and corpus size changes
        when adding new corpus units.
    2) Make sure the shorter units will be preferred when two or more units give the
        same unique signal (equivalent to the `REDUCE` logic).

    This solution was brainstormed together with @kcc, hopefully it looks good to
    the other people too. The proposed use case scenario:

    1) We have a `fuzz_target` binary and `existing_corpus` directory.
    2) We do fuzzing and write new units into the `new_corpus` directory.
    3) We want to merge the new corpus into the existing corpus and satisfy the
        points mentioned above.
    4) We create an empty directory `merged_corpus` and run the first merge step:

        ./fuzz_target -merge=1 -merge_control_file=MCF ./merged_corpus ./existing_corpus

        this provides the initial stats for `existing_corpus`, e.g. from the output:

        MERGE-OUTER: 3 new files with 11 new features added; 11 new coverage edges

    5) We recreate `merged_corpus` directory and run the second merge step:

        ./fuzz_target -merge=1 -merge_control_file=MCF ./merged_corpus ./existing_corpus ./new_corpus

        this provides the final stats for the merged corpus, e.g. from the output:

        MERGE-OUTER: 6 new files with 14 new features added; 14 new coverage edges

    Alternative solutions to this approach are:

    A) Store precise coverage information for every unit (not only unique signal).
    B) Execute the same two steps without reusing the control file.

    Either of these would be suboptimal as it would impose an extra disk or CPU load
    respectively, which is bad given the quadratic complexity in the worst case.

    Tested on Linux, Mac, Windows.

    Reviewers: morehouse, metzman, hctim, kcc

    Reviewed By: morehouse

    Subscribers: JDevlieghere, delcypher, mgrang, #sanitizers, llvm-commits, kcc

    Tags: #llvm, #sanitizers

    Differential Revision: (detail)
    by dor1s
  7. [ConstProp] move test file from InstSimplify; NFC

    These are constant folding tests; there is no code
    directly in InstSimplify for this. (detail)
    by spatel
  8. [InstSimplify] regenerate test CHECKs; NFC (detail)
    by spatel
  9. [Alignment][NFC] use llvm::Align for AsmPrinter::EmitAlignment

    This is patch is part of a series to introduce an Alignment type.
    See this thread for context:
    See this patch for the introduction of the type:

    Reviewers: courbet

    Subscribers: dschuff, sdardis, nemanjai, hiraditya, kbarton, jrtc27, MaskRay, atanasyan, jsji, llvm-commits

    Tags: #llvm

    Differential Revision: (detail)
    by gchatelet
  10. [LangRef] add link for fma intrinsic (detail)
    by spatel
  11. Bring back clang-x64-ninja-win7/windows7-buildbot

    Bring back clang-x64-ninja-win7/windows7-buildbot with correct info and 'autodetect' visual studio parameter.

    Reviewers: gkistanova

    Reviewed By: gkistanova

    Subscribers: llvm-commits

    Tags: #llvm

    Differential Revision: (detail)
    by itaraban
  12. [LangRef] fix punctuation; NFC (detail)
    by spatel
  13. gn build: add include_dir that's necessary after r371564 (detail)
    by nico
  14. [InstCombine] fold sign-bit compares of srem

    (srem X, pow2C) sgt/slt 0 can be reduced using bit hacks by masking
    off the sign bit and the module (low) bits:
    A '2' divisor allows slightly more folding:

    Any chance to remove an 'srem' use is probably worthwhile, but this is limited
    to the one-use improvement case because doing more may expose other missing
    folds. That means it does nothing for PR21929 yet:

    Differential Revision: (detail)
    by spatel
  15. [Alignment] Use llvm::Align in MachineFunction and TargetLowering - fixes mir parsing

    This catches malformed mir files which specify alignment as log2 instead of pow2.
    See for reference,

    This is patch is part of a series to introduce an Alignment type.
    See this thread for context:
    See this patch for the introduction of the type:

    Reviewers: courbet

    Subscribers: MatzeB, qcolombet, dschuff, arsenm, sdardis, nemanjai, jvesely, nhaehnle, hiraditya, kbarton, asb, rbar, johnrusso, simoncook, apazos, sabuasal, niosHD, jrtc27, MaskRay, zzheng, edward-jones, atanasyan, rogfer01, MartinMosbeck, brucehoult, the_o, PkmX, jocewei, jsji, Petar.Avramovic, asbirlea, s.egerton, pzheng, llvm-commits

    Tags: #llvm

    Differential Revision: (detail)
    by gchatelet
  16. [mips][msa] Fix infinite loop for mips.nori.b intrinsic

    When value of immediate in `mips.nori.b` is 255 (which has all ones in
    binary form as 8bit integer) DAGCombiner and Legalizer would fall in an
    infinite loop. DAGCombiner would try to simplify `or %value, -1` by
    turning `%value` into UNDEF. Legalizer will turn it back into `Constant<0>`
    which would then be again turned into UNDEF by DAGCombiner. To avoid this
    loop we make UNDEF legal for MSA int types on Mips.

    Patch by Mirko Brkusanin.

    Differential Revision: (detail)
    by atanasyan
  17. Fix -Wdocumentation warning - void function doesn't need a @returns. NFCI. (detail)
    by rksimon
  18. [Diagnostics] Add -Wsizeof-array-div

    Summary: Clang version of

    Reviewers: rsmith

    Differential Revision: (detail)
    by xbolva00
  19. [NFC] Updated objsize-64.ll test (detail)
    by xbolva00
  20. [NFC] Fixed test (detail)
    by xbolva00
  21. [InstCombine] Fixed handling of isOpNewLike (PR11748) (detail)
    by xbolva00
  22. [LoopInterchange] Drop unused splitInnerLoopHeader declaration. (detail)
    by fhahn

Started by timer (4 times)

This run spent:

  • 3 hr 38 min waiting;
  • 5 hr 14 min build duration;
  • 8 hr 53 min total from scheduled to completion.
Test Result (3 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

Compile Error

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

Ninja target failed

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