How to deliberately slow down compilation?

user_1823524 0
Viewed 402

There are a lot of questions asking how to speed up compilation of C++ code. I need to do the opposite.

I'm working with a software that monitors compiler invocation in order to do static code analysis. But if compiler process is closed too quickly, monitoring software can miss it. So I need to slow compilation down. I understand that's a terrible solution and hope it will be temporary.

I came up with two solutions:

  • Disable parallel build, enable preprocessor and compiler listing generation. It works but requires a lot of mouse clicking
  • Use compiler option to force inclusion of special header file that somehow slows compilation.

Unfortunately I couldn't come up with something simple to write and hard to compile at the same time. Using a lot of #warning seems to work but obviously clutters the output significantly.

I'm using Keil with armcc compiler, so I can use most of C++11 but maximum template recursion depth is just 63.

Preferably this should not produce any overhead for binary size or running time.

UPD: I'll try to clarify this a bit. I know that's a horrible idea, I know that this problem should be solved differently. I will try to solve it differently but I also want to explore this possibility.

compilation optimization c c++
2 Answers

Maybe this solution will be slow enough =), something like @NathanOliver propose. Its compile time table sine I use. It requires extra space, but you can tune it a little (table size and sine accuracy are template parameters of "staticSinus" function, hope you`ll find your best). https://godbolt.org/z/DYZDF5

user_92565800

You don't want to do anything of the sort. Here are some solutions, of varying degree of kludginess:

  1. Ideal solution: invoke the code analysis from the Makefile.

  2. Replace the compiler with an e.g. Python script that forwards the command-line to the compiler, then triggers the analysis tool.

  3. Monitor make instead of the compiler - it tends to live longer.

  4. Have a tiny wrapper script maintain a reference count in shared memory, and when the reference count is initially incremented, the wrapper should go to sleep for "long enough" after the compiler has finished. Monitor that script.

In a nutshell: the monitoring tool shouldn't be monitoring anything. The code analysis should be invoked from the build tool, i.e. given in the Makefile. If generating the Makefile by hand is too cumbersome, use cmake with ninja, or xmake with no dependencies. You can also generate whatever "project" file the IDE needs to make working on the project easier. But make something else than Keil-specific stuff be the source of truth for the project: it'll make everything go easy from then on.

user_13296520
Related