yrnkrn

2 ms·

1. 1.▲
   by yrnkrn 11y ago

   Note warp commits, the project is not too active. Maybe it's mature enough and requires few updates, I don't know as zapcc uses the clang Preprocessor and not warp. https://github.com/facebook/warp/commi
2. 2.▲
   by yrnkrn 11y ago

   You are correct, zapcc should be compared only to clang from the same svn. clang to gcc is another matter altogether. Even in first compilation, zapcc will cache between the first and second files compiled. The only case where there is no c
3. 3.▲
   by yrnkrn 11y ago

   We frequently merge with llvm svn, last time three days ago. It is a pain but that's the price to keep up with such a dynamic project. We do upstream enhancements and bug fixes for clang and LLVM code, see the {cfe,llvm}-commits mailin
4. 4.▲
   by yrnkrn 11y ago

   The optimizer is not disabled, few global optimizations are. The speedup is mostly the result of not having to reparse the headers, reinstantiate and codegen the generated templated code rather than skip minor opts. This is really slow proc
5. 5.▲
   by yrnkrn 11y ago

   We (zapcc) do nothing for link acceleration or debug info. The standard system linker is used. zapcc works well for C++ templates found in all modern C++ libraries.
6. 6.▲
   by yrnkrn 11y ago

   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&#x2F