3 ms·
I haven't seen anyone mention https://zapcc.com https://zapcc.com yet. I've been testing it and it works as advertised, cutting compile times by a factor of 5 o
by modeless 8y ago
I haven't seen anyone mention https://zapcc.com https://zapcc.com yet. I've been testing it and it works as advertised, cutting compile times by a factor of 5 or more in real world projects with zero code changes. It's both easier to use and faster than C++ modules could ever be, even in theory. It could go a long way to addressing one of Aras's complaints.
In order to improve C++ compilers, we are going to need to throw away some old assumptions about how they should work. Zapcc challenges the notion that the compiler should exit after compiling each file and start over with the next one. Perhaps some of the other issues Aras points out could be addressed by rethinking some assumptions. For example, tighter integration between the compiler and debugger could potentially make it feasible to debug optimized builds.
- jcelerier 8y ago> Zapcc challenges the notion that the compiler should exit after compiling each file and start over with the next one. this idea has been floating for a long time : ftp://gcc.gnu.org/pub/gcc/summit/2003/GCC%20Compile%20Server.pdf and https://gcc.gnu.org/wiki/IncrementalCompiler https://gcc.gnu.org/wiki/IncrementalCompiler sadly, it seems that modules has put these approaches on hold, even though I am pretty sure that modules won't solve the problem.