[PassManager] Detect analysis invalidations that take up the most compile time
Open
slow-compile
- Dominant language
- LLVM
- Stars
- 40.5k
- Forks
- 18.7k
- PR merge metrics
- PR metrics pending
Description
It would be cool to have infrastructure that would measure when an analysis is invalidated and then recomputed to see which passes invalidating analyses are taking up the most compile time. We have timers for analyses under `-time-passes`.
Contributor guide
Research direction
Start by reading the PassManager infrastructure and its existing analysis timers exposed through `-time-passes`. Trace where analyses are invalidated and recomputed, then determine how the timing data should identify invalidating passes that consume the most compile time. Done means the infrastructure reports those costs clearly and is covered by relevant tests, though the issue names no specific test file.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100