Skip to content

Profiling the Compiler #88

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
michaelwoerister opened this issue Mar 13, 2018 · 3 comments
Closed

Profiling the Compiler #88

michaelwoerister opened this issue Mar 13, 2018 · 3 comments
Labels
E-help-wanted Call for participation: extra help is wanted E-medium Difficulty: might require some prior knowledge or code reading

Comments

@michaelwoerister
Copy link
Member

It would be nice to have a section on how to profile the compiler, what tools to use, how to invoke them, and maybe a section on how to interpret results.

@mark-i-m mark-i-m added E-help-wanted Call for participation: extra help is wanted E-medium Difficulty: might require some prior knowledge or code reading labels Mar 13, 2018
@mark-i-m
Copy link
Member

@michaelwoerister Is this section (and its subsections) what you were thinking of?

https://rust-lang-nursery.github.io/rustc-guide/profiling.html

@michaelwoerister
Copy link
Member Author

@mark-i-m That's an excellent start! I would be great to also have some info on valgrind/cachegrind since those provide a slightly different and useful set of measurements but come with some caveats when invoking the profiler (i.e. making sure that the rustc executable is profiled, not cargo or the rustup wrapper).

@rylev
Copy link
Member

rylev commented Jul 4, 2021

Triage: Closing. Much like #175, this section already exists. Going to close this in favor of an issue specifically about valgrind/cachegrind.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E-help-wanted Call for participation: extra help is wanted E-medium Difficulty: might require some prior knowledge or code reading
Projects
None yet
Development

No branches or pull requests

3 participants