[XRay] Move-only Allocator, FunctionCallTrie, and Array


[XRay] Move-only Allocator, FunctionCallTrie, and Array

This change makes the allocator and function call trie implementations
move-aware and remove the FunctionCallTrie's reliance on a
heap-allocated set of allocators.

The change makes it possible to always have storage associated with
Allocator instances, not necessarily having heap-allocated memory
obtainable from these allocator instances. We also use thread-local
uninitialised storage.

We've also re-worked the segmented array implementation to have more
precondition and post-condition checks when built in debug mode. This
enables us to better implement some of the operations with surrounding
documentation as well. The trim algorithm now has more documentation
on the implementation, reducing the requirement to handle special
conditions, and being more rigorous on the computations involved.

In this change we also introduce an initialisation guard, through which
we prevent an initialisation operation from racing with a cleanup

We also ensure that the ThreadTries array is not destroyed while copies
into the elements are still being performed by other threads submitting

Note that this change still has an issue with accessing thread-local
storage from signal handlers that are instrumented with XRay. We also
learn that with the testing of this patch, that there will be cases
where calls to mmap(...) (through internal_mmap(...)) might be called in
signal handlers, but are not async-signal-safe. Subsequent patches will
address this, by re-using the BufferQueue type used in the FDR mode
implementation for pre-allocated memory segments per active, tracing

We still want to land this change despite the known issues, with fixes

Reviewers: mboerger, jfb

Subscribers: jfb, llvm-commits

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


dberrisDec 4 2018, 10:44 PM
Differential Revision
D54989: [XRay] Move-only Allocator, FunctionCallTrie, and Array