On Sun, 20 Nov 2011 03:43:20 -0800 Jeff Evarts <rivent...@gmail.com> wrote:
> I posted this question at irc://irc.oftc.net/#gcc and they suggested > that I pose it here instead. > > I do some "large-ish" builds (linux, gcc itself, etc) on a too-regular > basis, and I was wondering what could be done to speed things up. A > little printf-style checking hints to me that I might be spending the > majority of my time in CPP rather g++, gasm, ld, etc. Has anyone > (ever, regularly, or recently) built gcc (g++, gcpp) with profiling > turned on? Is it hard? Did you get good results? I'm not sure the question belongs to gcc@gcc.gnu.org, perhaps gcc-h...@gcc.gnu.org might be a better place. First, if you compile all GCC with -pg, then both the gcc driver and the cc1 compiler proper are profiled (and there can be a conflict). You can then run gcc with -v, and run again the cc1 which it gives you. Second, if you want some crude time report, gcc -ftime-report is simpler, but don't give you a very precise information. Regards. -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359 8, rue de la Faiencerie, 92340 Bourg La Reine, France *** opinions {are only mine, sont seulement les miennes} ***
