Jakub Jelinek via Gcc <gcc@gcc.gnu.org> writes: > On Tue, Mar 25, 2025 at 07:21:32AM +0300, Eldar Kusdavletov via Gcc wrote: >> *Dear GCC Mentoring Team,* >> I am writing to submit my proposal for the Google Summer of Code (GSoC) >> 2025 program, aiming to contribute to the GCC project by implementing a >> feature similar to Clang's -ftime-trace. This feature generates performance >> reports detailing the compiler's time distribution across various >> compilation phases, providing valuable insights for optimization. > > How is that different from GCC's -ftime-report or -ftime-report-details? > We've been tracking the time spent by different compilation phases for the > last 25 years...
-ftime-report* gives overall timings on phases, it does not give a line-by-line breakdown alongside the user's code. i.e. -ftime-trace helps to answer "which parts of my program are causing slow compilation?" See https://gcc.gnu.org/PR92396.
