Created by Pali on 2014-04-12 and last modified on 2018-10-22
Get this branch:
bzr branch lp:~pali/llvm/compiler-rt-trunk

Branch merges

Related bugs

Related blueprints

Branch information


Import details

Import Status: Reviewed

This branch is an import of the Subversion branch from http://llvm.org/svn/llvm-project/compiler-rt/trunk.

The next import is scheduled to run in 2 hours.

Last successful import was 3 hours ago.

Import started 3 hours ago on izar and finished 3 hours ago taking 30 seconds — see the log
Import started 9 hours ago on izar and finished 9 hours ago taking 30 seconds — see the log
Import started 15 hours ago on izar and finished 15 hours ago taking 25 seconds — see the log
Import started 21 hours ago on izar and finished 21 hours ago taking 25 seconds — see the log
Import started on 2018-10-21 on alnitak and finished on 2018-10-21 taking 25 seconds — see the log
Import started on 2018-10-20 on izar and finished on 2018-10-20 taking 25 seconds — see the log
Import started on 2018-10-20 on izar and finished on 2018-10-20 taking 25 seconds — see the log
Import started on 2018-10-20 on alnitak and finished on 2018-10-20 taking 1 minute — see the log
Import started on 2018-10-20 on izar and finished on 2018-10-20 taking 25 seconds — see the log
Import started on 2018-10-19 on alnitak and finished on 2018-10-19 taking 25 seconds — see the log

Recent revisions

10678. By dberris 5 hours ago

[XRay] Handle allocator exhaustion in segmented array

This change allows us to handle allocator exhaustion properly in the
segmented array implementation. Before this change, we relied on the
caller of the `trim` function to provide a valid number of elements to
trim. This change allows us to do the right thing in case the elements
to trim is greater than the size of the container.

Reviewers: mboerger, eizan

Subscribers: llvm-commits

Differential Revision: https://reviews.llvm.org/D53484

10677. By devnexen 10 hours ago

[Sanitizer] openbsd does not have sysctlbyname call

Enabling only for FreeBSD.

Reviewers: krytarowski, vitalybuka

Reviewed By: krytarowski

Differential Revision: https://reviews.llvm.org/D53413

10676. By ctopper on 2018-10-20

[X86][compiler-rt] Add additional CPUs and features to the cpu detection to match libgcc

Summary: This patch adds additional features and cpus from libgcc. Unfortunately we've overflowed the existing 32-bits of features so we had to add a new __cpu_features2 variable to hold the additional bits. This matches libgcc as far as I can tell.

Reviewers: echristo

Reviewed By: echristo

Subscribers: dberris, llvm-commits

Differential Revision: https://reviews.llvm.org/D53461

10675. By dyung on 2018-10-19

Revert commit r344670 as the test fails on a bot http://lab.llvm.org:8011/builders/clang-cmake-armv7-full/builds/2683/.

10674. By danalbert on 2018-10-18

[compiler-rt] Don't explicitly set CMAKE_CXX_FLAGS.

C++ flags should not be used for not-C++ files as it may trigger
-Werror=unused-command-line-argument. CMake will use CMAKE_C_FLAGS,
CMAKE_CXX_FLAGS, and CMAKE_ASM_FLAGS as appropriate implicitly, so
this does not need to be explicitly handled here.

This change depends on https://reviews.llvm.org/D53301, since one of
the builders depended on this behavior because it was not configuring

Reviewers: eugenis, vitalybuka

Reviewed By: eugenis, vitalybuka

Subscribers: dberris, mgorny, delcypher, #sanitizers, llvm-commits

Differential Revision: https://reviews.llvm.org/D53335

10673. By dberris on 2018-10-17

[XRay][compiler-rt] Generational Buffer Management

This change updates the buffer queue implementation to support using a
generation number to identify the lifetime of buffers. This first part
introduces the notion of the generation number, without changing the way
we handle the buffers yet.

What's missing here is the cleanup of the buffers. Ideally we'll keep
the two most recent generations. We need to ensure that before we do any
writes to the buffers, that we check the generation number(s) first.

Those changes will follow-on from this change.

Depends on D52588.

Reviewers: mboerger, eizan

Subscribers: llvm-commits, jfb

Differential Revision: https://reviews.llvm.org/D52974

10672. By phosek on 2018-10-16

[XRay] Use fully qualified name for LogWriter

This avoids the build error in newer versions of GCC.

10671. By phosek on 2018-10-16

[XRay] Encapsulate all FD log related logic into a class

This abstracts away the file descriptor related logic which makes it
easier to port XRay to platform that don't use file descriptors or
file system for writing the log data, such as Fuchsia.

Differential Revision: https://reviews.llvm.org/D52161

10670. By dberris on 2018-10-15

[XRay][compiler-rt] FDR Mode Controller

This change implements a controller for abstracting away the details of
what happens when tracing with FDR mode. This controller type allows us
to test in isolation the various cases where we're encountering function
entry, exit, and other kinds of events we are handling when FDR mode is

This change introduces a number of testing facilities we've needed to
better support expressing the conditions we need for the unit tests. We
leave some TODOs for moving those utilities into the LLVM project,
sitting in the `Testing` library, to make matching conditions on XRay
`Trace` instances through googlemock more manageable and declarative.

We don't wire in the controller right away, to allow us to incrementally
update the implementation(s) as we increase testing coverage of the
controller type. There's a need to re-think the way we're managing
buffers in a multi-threaded environment, which is more invasive than
this implementation.

This step in the process allows us to encode our assumptions in the
implementation of the controller, and then evolve the buffer queue
implementation to support generational buffer management to ensure we
can continue to support the cases we're already supporting with the

Reviewers: mboerger, eizan

Subscribers: mgorny, llvm-commits, jfb

Differential Revision: https://reviews.llvm.org/D52588

10669. By metzman on 2018-10-14

[libfuzzer][Windows] Silence linker warning in unittest

Silence warning when linking unittest binary by not passing
-lstdc++ to the linker since it is ignored.

Reviewers: morehouse

Reviewed By: morehouse

Subscribers: mgorny

Differential Revision: https://reviews.llvm.org/D53225

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.


No subscribers.