News for hackers. Stuff that matters.
Re:Zapcc: A faster C++ compiler by IshKebab on Saturday May 23, 2015 @12:03PM (#9593311)
I don't think this is snake oil. The reasons that are typically given for not automatically pre-compiling headers (we're not talking about manually specified pre-compiled headers here) can all be worked around.

For example, some might say that you can't automatically cache headers because of code like this:

// file1.cpp

#include "foo.h"

// file2.cpp

#define float double

#include "foo.h"

But if you're a bit clever about it you should be able to cache opportunistically and then detect if your cache is invalidated.

Re:Zapcc: A faster C++ compiler by yrnkrn on Sunday May 24, 2015 @04:09AM (#9595659)
I am the prinicipal developer of zapcc. We have added a FAQ

http://www.zapcc.com/faq/

and more tech details in the cfe-dev mailing list

http://lists.cs.uiuc.edu/pipermail/cfe-dev/2015-May/043174.h...

To the point, zapcc will not reprocess foo.h. This is a limitation. However, zapcc does deal with templates instantiations and such correctly and fast, such as boost various libraries, Eigen and LLVM source code.