The refactoring encapsulates frequency calculation in MachineBlockFrequencyInfo,
and renames the API to clarify its motivation. It should clarify
frequencies may not be reset 'freely' by users of the analysis, as the
API serves as a partial update to avoid a full analysis recomputation.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Perhaps also keep setBlockFreq as a lower level interface? I am surprised that edge splitting is the only one user of it.
Comment Actions
We can always add it back. Its absence makes things easier to a reader, I think, because it becomes more clear when the analysis result undergoes mutations - i.e. whenever the pass manager requests it, and during edge splitting, as a performance optimization.