diff options
| author | Jubilee <workingjubilee@gmail.com> | 2025-02-13 21:37:51 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-02-13 21:37:51 -0800 |
| commit | 6c1768e66cc08b1f1df53ee2ac1436359df5dc9d (patch) | |
| tree | 094b1d88f5a59c41142e6dccb79a831a63ac8642 /compiler/rustc_codegen_gcc | |
| parent | dfc235f80c4f3d94f91043cc7795fe72709b11d2 (diff) | |
| parent | 521cbd36fa1cc645a3682fe429b4d636b16b6fbe (diff) | |
| download | rust-6c1768e66cc08b1f1df53ee2ac1436359df5dc9d.tar.gz rust-6c1768e66cc08b1f1df53ee2ac1436359df5dc9d.zip | |
Rollup merge of #136924 - Kobzol:bootstrap-tracing, r=jieyouxu
Add profiling of bootstrap commands using Chrome events Since we now have support for tracing in bootstrap, and the execution of most commands is centralized within a few functions, it's quite trivial to also trace command execution, and visualize it using the Chrome profiler. This can be helpful both to profile what takes time in bootstrap and also to get a visual idea of what happens in a given bootstrap invocation (since the execution of external commands is usually the most interesting thing). This is how it looks:  I first tried to use [tracing-flame](https://github.com/tokio-rs/tracing/tree/master/tracing-flame), but the output wasn't very useful, because the event/stackframe names were bootstrap code locations, instead of the command contents. r? ``@jieyouxu``
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions