diff options
author | Sam McCall <sam.mccall@gmail.com> | 2018-01-26 09:00:30 +0000 |
---|---|---|
committer | Sam McCall <sam.mccall@gmail.com> | 2018-01-26 09:00:30 +0000 |
commit | 1b475a1ad0775a33a02ae5df0d2544b721bbc598 (patch) | |
tree | e83f8acf75d6901cb15ba08012b567a1205c9f87 /llvm/lib/Target/ARM/Disassembler/ARMDisassembler.cpp | |
parent | d1a6646e594498a0f0561853195290f0076f7442 (diff) | |
download | bcm5719-llvm-1b475a1ad0775a33a02ae5df0d2544b721bbc598.tar.gz bcm5719-llvm-1b475a1ad0775a33a02ae5df0d2544b721bbc598.zip |
[clangd] Modify the Span API so that Spans propagate with contexts.
Summary:
This is probably the right behavior for distributed tracers, and makes unpaired
begin-end events impossible without requiring Spans to be bound to a thread.
The API is conceptually clean but syntactically awkward. As discussed offline,
this is basically a naming problem and will go away if (when) we use TLS to
store the current context.
The apparently-unrelated change to onScopeExit are because its move semantics
broken if Func is POD-like since r322838. This is true of function pointers,
and the lambda I use here that captures two pointers only.
I've raised this issue on llvm-dev and will revert this part if we fix it in
some other way.
Reviewers: ilya-biryukov
Subscribers: klimek, jkorous-apple, ioeric, cfe-commits
Differential Revision: https://reviews.llvm.org/D42499
llvm-svn: 323511
Diffstat (limited to 'llvm/lib/Target/ARM/Disassembler/ARMDisassembler.cpp')
0 files changed, 0 insertions, 0 deletions