Started 11 mo ago
Took 14 min

Success Build clang-r362860-t57342-b57342.tar.gz (Jun 7, 2019 7:06:58 PM)


No known issues detected

Build Log

Revision: 362564
  1. Visualizer for APInt and remove obsolete visualizer

    Visualizer for the simple case of APInt (uints < 2^64)
    as will be required  for Clang ConstantArrayType visualizer.
    Also, removed obsolete VS2013 SmallVectorVisualizer as VS2013
    is no longer supported. (detail)
    by mps
  2. Factor out SelectionDAG's switch analysis and lowering into a separate component.

    In order for GlobalISel to re-use the significant amount of analysis and
    optimization code in SDAG's switch lowering, we first have to extract it and
    create an interface to be used by both frameworks.

    No test changes as it's NFC.

    Differential Revision: (detail)
    by Amara Emerson
Revision: 362564
  1. DebugInfo: Add support for 'nodebug' attribute on typedefs and alias templates

    Seems like a logical extension to me - and of interest because it might
    help reduce the debug info size of libc++ by applying this attribute to
    type traits that have a disproportionate debug info cost compared to the
    benefit (& possibly harm/confusion) they cause users. (detail)
    by dblaikie
  2. [analyzer] Add werror flag for analyzer warnings

    We're using the clang static analyzer together with a number of
    custom analyses in our CI system to ensure that certain invariants
    are statiesfied for by the code every commit. Unfortunately, there
    currently doesn't seem to be a good way to determine whether any
    analyzer warnings were emitted, other than parsing clang's output
    (or using scan-build, which then in turn parses clang's output).
    As a simpler mechanism, simply add a `-analyzer-werror` flag to CC1
    that causes the analyzer to emit its warnings as errors instead.
    I briefly tried to have this be `Werror=analyzer` and make it go
    through that machinery instead, but that seemed more trouble than
    it was worth in terms of conflicting with options to the actual build
    and special cases that would be required to circumvent the analyzers
    usual attempts to quiet non-analyzer warnings. This is simple and it
    works well.

    Reviewed-By: NoQ, Szelethusw
    Differential Revision: (detail)
    by kfischer
Revision: 362564
  1. Experimantal dfsan mode "fast16labels=1"

    dfsan mode "fast16labels=1".
    In this mode the labels are treated as 16-bit bit masks.

    Reviewers: pcc

    Reviewed By: pcc

    Subscribers: delcypher, #sanitizers, llvm-commits

    Tags: #llvm, #sanitizers

    Differential Revision: (detail)
    by kcc

Started by upstream project relay-lnt-ctmark build number 8524
originally caused by:

This run spent:

  • 9 min 36 sec waiting;
  • 14 min build duration;
  • 14 min total from scheduled to completion.