Started 5 mo 16 days ago
Took 42 min

Success Build clang-r362864-t57344-b57344.tar.gz (Jun 7, 2019 7:56:17 PM)


No known issues detected

Build Log

Revision: 362564
  1. gn build: Merge r362857 (detail)
    by nico
  2. [llvm-objcopy][MachO] Recompute and update offset/size fields in the writer

    Recompute and update offset/size fields so that we can implement llvm-objcopy options like --only-section.

    This patch is the first step and focuses on supporting load commands that covered by existing tests: executable files and
    dynamic libraries are not supported.

    Reviewers: alexshap, rupprecht, jhenderson

    Reviewed By: alexshap, rupprecht

    Subscribers: compnerd, jakehehrlich, llvm-commits

    Tags: #llvm

    Differential Revision: (detail)
    by seiya
  3. 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
  4. 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 aemerson
  5. LoopDistribute: Add testcase where SCEV wants to insert a runtime

    Only the memory based checks were being tested. Prepare for fix in
    convergent handling. (detail)
    by arsenm
  6. [GVN] non-functional code movement

    Summary: Move some code around, in preparation for later fixes
    to the non-integral addrspace handling (D59661)

    Patch By Jameson Nash <>

    Reviewed By: reames, loladiro
    Differential Revision: (detail)
    by kfischer
  7. AMDGPU: Force skips around traps (detail)
    by arsenm
  8. [COFF] Fix /export:foo=bar when bar is a weak alias

    When handling exports from the command line or from .def files, the
    linker does a "fuzzy" string lookup to allow finding mangled symbols.
    However, when the symbol is re-exported under a new name, the linker has
    to transfer the decorations from the exported symbol over to the new
    name. This is implemented by taking the mangled symbol that was found in
    the object and replacing the original symbol name with the export name.

    Before this patch, LLD implemented the fuzzy search by adding an
    undefined symbol with the unmangled name, and then during symbol
    resolution, checking if similar mangled symbols had been added after the
    last round of symbol resolution. If so, LLD makes the original symbol a
    weak alias of the mangled symbol. Later, to get the original symbol
    name, LLD would look through the weak alias and forward it on to the
    import library writer, which copies the symbol decorations. This
    approach doesn't work when bar is itself a weak alias, as is the case in
    asan. It's especially bad when the aliasee of bar contains the string
    "bar", consider "bar_default". In this case, we would end up exporting
    the symbol "foo_default" when we should've exported just "foo".

    To fix this, don't look through weak aliases to find the mangled name.
    Save the mangled name earlier during fuzzy symbol lookup.

    Fixes PR42074

    Reviewers: mstorsjo, ruiu

    Subscribers: thakis, llvm-commits

    Tags: #llvm

    Differential Revision: (detail)
    by rnk
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
Revision: 362564
  1. Fix some incorrect std::function tests (detail)
    by ericwf

Started by upstream project relay-test-suite-verify-machineinstrs build number 5394
originally caused by:

This run spent:

  • 5.1 sec waiting;
  • 42 min build duration;
  • 42 min total from scheduled to completion.