Started 8 mo 13 days ago
Took 16 min on green-dragon-22

Failed Build rL:372021 - C:372015 - #617 (Sep 16, 2019 12:01:32 PM)

  • : 372021
  • : 372015
  • : 371997
  • : 364589
  • : 371835
  • : 372016
  • : 372008
  1. [LTO][Legacy] Add new C inferface to query libcall functions

    This is needed to implemented the same approach as lld (implemented in r338434)
    for how to handling symbols that can be generated by LTO code generator
    but not present in the symbol table for linker that uses legacy C APIs.

    libLTO is in charge of providing the list of symbols. Linker is in
    charge of implementing the eager loading from static libraries using
    the list of symbols.


    Reviewers: tejohnson, bd1976llvm, deadalnix, espindola

    Reviewed By: tejohnson

    Subscribers: emaste, arichardson, hiraditya, MaskRay, dang, kledzik, mehdi_amini, inglorion, jkorous, dexonsmith, ributzka, llvm-commits

    Tags: #llvm

    Differential Revision: (detail/ViewSVN)
    by steven_wu
  2. [PGO] Use linkonce_odr linkage for __profd_ variables in comdat groups

    This fixes relocations against __profd_ symbols in discarded sections,
    which is PR41380.

    In general, instrumentation happens very early, and optimization and
    inlining happens afterwards. The counters for a function are calculated
    early, and after inlining, counters for an inlined function may be
    widely referenced by other functions.

    For C++ inline functions of all kinds (linkonce_odr &
    available_externally mainly), instr profiling wants to deduplicate these
    __profc_ and __profd_ globals. Otherwise the binary would be quite

    I made __profd_ and __profc_ comdat in r355044, but I chose to make
    __profd_ internal. At the time, I was only dealing with coverage, and in
    that case, none of the instrumentation needs to reference __profd_.
    However, if you use PGO, then instrumentation passes add calls to
    __llvm_profile_instrument_range which reference __profd_ globals. The
    solution is to make these globals externally visible by using
    linkonce_odr linkage for data as was done for counters.

    This is safe because PGO adds a CFG hash to the names of the data and
    counter globals, so if different TUs have different globals, they will
    get different data and counter arrays.

    Reviewers: xur, hans

    Differential Revision: (detail/ViewSVN)
    by rnk

Started by an SCM change

This run spent:

  • 9 min 35 sec waiting;
  • 16 min build duration;
  • 26 min total from scheduled to completion.
LLVM/Clang Warnings: 2 warnings.

Identified problems

Compile Error

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

Missing test results

The test result file Jenkins is looking for does not exist after the build.
Indication 2

Ninja target failed

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