diff options
| author | Tomasz Miąsko <tomasz.miasko@gmail.com> | 2021-11-05 00:00:00 +0000 |
|---|---|---|
| committer | Tomasz Miąsko <tomasz.miasko@gmail.com> | 2021-11-05 17:47:11 +0100 |
| commit | 5a09e1213543fca0cbc9a0a61643e8d1bd4fccd8 (patch) | |
| tree | ad40a748f2f13decb0537bf651da8d2c0230e568 /compiler/rustc_mir_transform/src/coverage/mod.rs | |
| parent | d22dd65835190278f315e06442614142653ec98f (diff) | |
| download | rust-5a09e1213543fca0cbc9a0a61643e8d1bd4fccd8.tar.gz rust-5a09e1213543fca0cbc9a0a61643e8d1bd4fccd8.zip | |
Initialize LLVM time trace profiler on each code generation thread
In https://reviews.llvm.org/D71059 LLVM 11, the time trace profiler was extended to support multiple threads. `timeTraceProfilerInitialize` creates a thread local profiler instance. When a thread finishes `timeTraceProfilerFinishThread` moves a thread local instance into a global collection of instances. Finally when all codegen work is complete `timeTraceProfilerWrite` writes data from the current thread local instance and the instances in global collection of instances. Previously, the profiler was intialized on a single thread only. Since this thread performs no code generation on its own, the resulting profile was empty. Update LLVM codegen to initialize & finish time trace profiler on each code generation thread.
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/mod.rs')
0 files changed, 0 insertions, 0 deletions
