Skip to content

Explain how to benchmark the compiler #175

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.

Sign up for GitHub

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

Jump to bottom
Closed
orium opened this issue Jul 30, 2018 · 3 comments
Closed

Explain how to benchmark the compiler #175

orium opened this issue Jul 30, 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

@orium
Copy link
Member

orium commented Jul 30, 2018

No description provided.

@mark-i-m
Copy link
Member

@nnethercote @wesleywiser Would either of you be able to write something for this?

@nnethercote
Copy link
Contributor

https://github.com/rust-lang-nursery/rustc-perf/blob/master/collector/README.md pretty much has this information. Maybe the guide should just point to that document?

@mark-i-m mark-i-m mentioned this issue Aug 31, 2018
Merged
@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 Jan 23, 2019
@rylev
Copy link
Member

rylev commented Jul 4, 2021

Triage: Closing. This section already exists. It's not perfect, but we have other issues like #1150 that provide tracking for more specific issues.

@rylev rylev closed this as completed Jul 4, 2021
@rylev rylev mentioned this issue Jul 4, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
No milestone
Development

No branches or pull requests
4 participants
@rylev @nnethercote @orium @mark-i-m