Profiling the C++ compilation process
I tend to write rather large templated header-only C++ libraries and my users commonly complain about compilation times. After thinking about the matter, it occurred to me that I have no idea where the time is going. Is there some simple way to profile the C++ compilation process with common compilers, such as g++, icc, and xlC? For instance, is it possible to get an idea of how much time is spent within each of the phases of C++ compilation?
For GCC there are debugging options to find how much time is spent within each of the phases of C++ compilation?
-Q Makes the compiler print out each function name as it is compiled, and print some statistics about each pass when it finishes.
-ftime-report Makes the compiler print some statistics about the time consumed by each pass when it finishes.
Passes are described in GCCINT 9: Passes and Files of the Compiler.
You can post output of g++ compilation of single source file with -v -ftime-report here to discuss it. There could be some help on the GCC mailing list.
For compilers other than GCC (or GCC more ancient than 3.3.6) see the other options in this thread.
There's a tool from the Boost project, which could be useful for pretty much any compiler and build system.
The tool requires source code instrumentation with TEMPLATE_PROFILE_ENTER() and TEMPLATE_PROFILE_EXIT() macro calls. These macros then generate specific diagnostics (warnings) at compile-time, which are timed and collected along with instantiation callstacks (which consequently allow building and visualizing callgraphs) by a script. Not bad, IMO.
I didn't use it yet though.
我还没有尝试过，但templight看起来很有希望：https：//github.com/mikael-s-persson/templight
链接地址: http://www.djcxy.com/p/43848.html上一篇: 'call dword ptr [mem32]'问题的操作码和ModRM？
下一篇: 剖析C ++编译过程