We should have a way to calculate how long each item in your codebase takes to compile. Conceptually this would work by grouping the measureme data by DefId/NodeId or some other identifier rather than by the query name. We can then output a sorted list of items by how long each takes.
For example, the output might look like this:
$ summarize code-profile /path/to/rustc-results
Total time in rustc: 120 seconds
----------------------------------------
| % time | Item |
| ------ | -----------------------------
| 20.4% | example::foo::bar::clone() |
| 10.2% | example::baz::widget::bla() |
(more rows)
This will require changes to the profiling code in rustc to record DefIds or NodeIds for each query.
We should have a way to calculate how long each item in your codebase takes to compile. Conceptually this would work by grouping the
measuremedata byDefId/NodeIdor some other identifier rather than by the query name. We can then output a sorted list of items by how long each takes.For example, the output might look like this:
This will require changes to the profiling code in rustc to record
DefIds orNodeIds for each query.