`benchmark_codegen_test` output should show critical path nodes in each stage
Open
delay model
enhancement
ir
scheduler
- Dominant language
- C++
- Stars
- 1.9k
- Forks
- 283
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 135
Description
Right now it just shows the stages and number of nodes / delay, but would be helpful to be able to see how the critical path nodes ended up landing in the various stages, e.g. to see if anything hopped the boundary from stage to stage as the user tweaked the input.
Contributor guide
Assessment
This issue has not been assessed yet.