diff options
| author | Dylan DPC <99973273+Dylan-DPC@users.noreply.github.com> | 2022-04-05 22:58:55 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-04-05 22:58:55 +0200 |
| commit | c5e7e952925be74fc7dd6a2fac8e16df9e2044f6 (patch) | |
| tree | 74472c12a12821573235732c3cbbf97bd9fdbcd2 /compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp | |
| parent | d2e1e6dc759ef6c56e68382a148ed7181ab3a18f (diff) | |
| parent | 9ac8d2fe4ed0f5312bcd74c05f441d23536c1a8f (diff) | |
| download | rust-c5e7e952925be74fc7dd6a2fac8e16df9e2044f6.tar.gz rust-c5e7e952925be74fc7dd6a2fac8e16df9e2044f6.zip | |
Rollup merge of #95473 - lqd:macro-expansion, r=petrochenkov
track individual proc-macro expansions in the self-profiler As described in [this zulip thread](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/Macro.20expansion.20performance.20on.20complex.20macros/near/275063190), users don't currently have a lot of information to diagnose macro expansion performance issues. That comment suggests using the macro names to add further timing information. This PR starts to do this for proc-macros which have the same issue, and performance problems happening in the wild in [this other zulip thread](https://rust-lang.zulipchat.com/#narrow/stream/247081-t-compiler.2Fperformance/topic/Identifying.20proc-macro.20slowdowns) could be helped by such information. It uses the available proc-macro name to track their individual expansions with self-profiling events. r? `@Aaron1011` who mentioned this idea originally
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp')
0 files changed, 0 insertions, 0 deletions