aaboud added a comment. > How are you measuring the build time? Total time for, say "ninja clang" with > full parallelism? That'd be hard to measure the actual impact (since it could > be the link time or other things are dominating, etc). If you have a reliable > way to time (I'm assuming Intel has lots of tools for measuring compiler > performance) the compilation, get a sense of the variance, etc (& link time, > to get a sense of how much the larger inputs affect linker performance) would > be useful.
I did a manual measurement, but I believe it is representative. I used "time" tool to measure the whole time of the build (compile + link). - time make -j8 Also, notice that I limited the targets to X86 only, so it was not a full build of LLVM. - -DLLVM_OPTIMIZED_TABLEGEN=ON -DLLVM_TARGETS_TO_BUILD="X86" -DCMAKE_CXX_FLAGS="-fstandalone-debug" -DCMAKE_C_FLAGS="-fstandalone-debug" However, as I already said, it should answer the time change and size question fairly enough. > Does GCC have a command line option for this that we could mirror? GCC emits macro debug info when when build with -g3. https://reviews.llvm.org/D16135 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
