diff options
| author | bors <bors@rust-lang.org> | 2021-11-06 09:55:50 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2021-11-06 09:55:50 +0000 |
| commit | 3cd3bbecc5e498465e89be8a33d2936aaebed0bf (patch) | |
| tree | 8f46689d0f1f642c432677bb7eca074399e63fa7 /library/std/src/os/unix/net/addr.rs | |
| parent | 7276a6a11768634c1e7df5605a83a0f117302c50 (diff) | |
| parent | 5a09e1213543fca0cbc9a0a61643e8d1bd4fccd8 (diff) | |
| download | rust-3cd3bbecc5e498465e89be8a33d2936aaebed0bf.tar.gz rust-3cd3bbecc5e498465e89be8a33d2936aaebed0bf.zip | |
Auto merge of #90617 - tmiasko:time-trace-threads, r=wesleywiser
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. cc `@tmandry` r? `@wesleywiser`
Diffstat (limited to 'library/std/src/os/unix/net/addr.rs')
0 files changed, 0 insertions, 0 deletions
