http://www.zapcc.com/case-studies/compiling-boost/
even their first compilation (the one you still need to perform when using ccache) is twice as fast as GCC.
In any case, I think the primary audience for this is people using clang, not GCC.
Even in first compilation, zapcc will cache between the first and second files compiled. The only case where there is no caching is when zapccs starts or re-startes, for example when compilation flags are changed.
Also, ccache generates the preprocessor output, even in those cases when it deduces that compiling is unnecessary (and just pulls out a previously made object file). It makes that deduction based on the hash over the preprocessor output.
So a cache of what was generated last time, which will have to be replaced if the input files or compile command changes. So, a lot like ccache. Which is why I asked.