about summary refs log tree commit diff
path: root/compiler/rustc_codegen_llvm/src/errors.rs
diff options
context:
space:
mode:
authorStuart Cook <Zalathar@users.noreply.github.com>2025-08-08 12:52:51 +1000
committerGitHub <noreply@github.com>2025-08-08 12:52:51 +1000
commit2b7659ca0f498c2ade596b5bb8a60be4de556d14 (patch)
tree27d512461d7486a88c61668206fe71f9c27a0a00 /compiler/rustc_codegen_llvm/src/errors.rs
parentaf33da37f6465a7ffc2e5f87b0feff477dd4e595 (diff)
parentd857d54110fcdf72c71312cf38186b9d66c52df8 (diff)
downloadrust-2b7659ca0f498c2ade596b5bb8a60be4de556d14.tar.gz
rust-2b7659ca0f498c2ade596b5bb8a60be4de556d14.zip
Rollup merge of #144899 - Kobzol:cgu-reuse, r=saethlin
Print CGU reuse statistics in `-Zprint-mono-items`

I'm trying to expose more information about incremental profiling from rustc (https://rust-lang.zulipchat.com/#narrow/channel/131828-t-compiler/topic/Profiling.2Fanalysis.20of.20incremental.20builds/with/531383501). One of the things that would be quite useful to expose is the CGU reuse state, so that when you do a rebuild, you can see all the CGUs (and all the functions) that had to be recompiled.

Currently, we have (AFAIK) two ways of outputting monomorphization statistics:
1) `-Zdump-mono-stats` outputs statistics about number of instantiations and expected compilation cost of individual functions in the local crate being compiled. It can be outputted either as Markdown or JSON.
2) `-Zprint-mono-items` outputs a pair (item, CGU) for each monomorphized item.

I was thinking about recording CGU statistics in the self-profile output, but I realized that as a simpler step, we could just add CGU reuse data to `-Zprint-mono-items`, as an additional output. That is what this PR does.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions