diff options
| author | Dean Michael Berris <dberris@google.com> | 2017-05-01 00:52:57 +0000 |
|---|---|---|
| committer | Dean Michael Berris <dberris@google.com> | 2017-05-01 00:52:57 +0000 |
| commit | d816020bbf906c6452e8911151abb688176c2ef5 (patch) | |
| tree | ea084acf538a4f068cf835884cff8e6d026c88fb /www | |
| parent | aa1c977562f63984d19f8c1fc97adb94b9e493eb (diff) | |
[XRay][compiler-rt] Document and update the XRay Logging API
Summary:
In this patch we document the requirements for implementations that want
to install handlers for the dynamically-controlled XRay "framework".
This clarifies what the expectations are for implementations that
want to install their handlers using this API (similar to how the FDR
logging implementation does so). It also gives users some guarantees on
semantics for the APIs.
If all goes well, users can decide to use the XRay APIs to control the
tracing/logging at the application level, without having to depend on
implementation details of the installed logging implementation. This
lets users choose the implementation that comes with compiler-rt, or
potentially multiple other implementations that use the same APIs.
We also add one convenience function (__xray_remove_log_impl()) for
explicitly removing the currently installed log implementation.
Reviewers: kpw, pelikan
Subscribers: llvm-commits
Differential Revision: https://reviews.llvm.org/D32579
git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@301784 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'www')
0 files changed, 0 insertions, 0 deletions