On Tue, Oct 01, 2024 at 18:06:35 +0200, Richard Biener via Gcc wrote:
> Analyze where the compile time is spent and where memory is spent.
> Identify unfitting data structures and algorithms causing the issue.
> Replace with better ones. That’s what I do for these kind of issues
> in the middle end.
To this end, are there any plans or progress to implementing
`-ftime-trace` profiling output? (It's a clang thing, but there is
tooling that would be able to use GCC's reports if it made them.)
https://aras-p.info/blog/2019/01/12/Investigating-compile-times-and-Clang-ftime-report/
This is also available to do build-wide perf visualization (when using
`ninja`) with this tool that reads `-ftime-trace` files when they're
available):
https://github.com/nico/ninjatracing
(FWIW, I have a dream to have CI builds be able to save out this
information so that longer-term perf trends can be investigated. If this
comes up with project changes to do less silly template magic or
improvements to compilers to be faster, all the better.)
Thanks,
--Ben
