>
> I was wondering why in ccache we are expanding @file
>
> https://github.com/venkrao/ccache-1/blob/59e5244dd79b0fc7df682c8f3c05b778a3d00f91/ccache.c#L1951
@file is expanded so that ccache can inspect the options in the file just
like options given on the command line. The alternative is to not
Hello,
I was wondering why in ccache we are expanding @file
https://github.com/venkrao/ccache-1/blob/59e5244dd79b0fc7df682c8f3c05b778a3d00f91/ccache.c#L1951
Essentially, the arguments that are to be listed in @file are those that
affect the preprocessor.
Is it safe to just not expand the arguments
> Or perhaps ccache should just cache stdout. distcc sends it across
> the network alongside stderr.
>
> I'm not sure why writing to stdout forces a cache miss.
It's because is also very hard to accurately cache both stderr and
stdout because of the timing of lines between them. To really
accur
On 17 Feb 2003, Anders Furuhed wrote:
> I'm considering whether to make a patch for our own use that accepts
> a parameterized CCACHE_WHATEVER regexp that is used to filter the
> stdout result before deciding not to cache.
Or perhaps ccache should just cache stdout. distcc sends it across
the n
I was just about to start using ccache with distcc and didn't know the best way
to go about, only to discover a just-in-time release that makes it easy! Thanks!
Last week we started to use the Intel compiler in parallel with gcc. The Intel
compilers produce a number of cool but unnecessary messa
