This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Profiling gcc itself
On Sun, Nov 20, 2011 at 7:50 PM, Jeff Evarts <riventree@gmail.com> wrote:
> Apparently my question "Has anyone done X and what were the results"
> has been mysteriously translated into "The GCC compiler is way too
> slow and what are you lazy developers going to do to speed up my
> compiles?!?". I will be more careful to shower my favorite compiler
> and its contributors with praise before posting another question here.
> :)
>
> To clarify: I wanted to know if anyone had performed a profiling run
> on gcc, whether that was a regular occurrence, and what the results
> (if any) were.
Yes, a lot of groups perform detailed profiling and analysis of GCC,
including Google and SuSE. You can look at GCC Bugzilla PR 45375 for
detailed analysis of GCC LTO performance. Or PR 26854.
GCC's performance scales a lot with memory usage, so most recent work
has focused on reducing GCC's memory footprint and using more compact
and efficient data structures.
- David