Hi Francois, On 08/09/11 08:43 +1200, Francois Marier said ... > On 2008-09-10 at 17:10:43, Y Giridhar Appaji Nag wrote: > > Or rather, we don't delete the temporary pre-processor file. I did not > > look at the code too much but we shouldn't have to cache this file also. > > Well, that works for the first run when the output of the compilation is not > in cache. Then on the second run, gcc will not be called at all so these > temporary files will not be generated as the object files will be copied > back from cache.
Sure, I understand that. And this is exactly what happens with the .s file (the other file generated apart from the .i file). > So for that option to be useful (and consistent) regardless of whether or > not the temp file is in cache, then I think that you'd have to save the > extra temporary files in your ~/.ccache/ directory. I agree. And the solution that I indicated would at-best make it consistent with the behaviour (creation and retaining) in case of the ".s" file. And now that we've thought and discussed this, I guess this is a rather specialised request, so please feel free to mark this as wontfix. Using CCACHE_DISABLE is a viable workaround I think. Cheers, Giridhar -- Y Giridhar Appaji Nag | http://appaji.net/
signature.asc
Description: Digital signature
