On 23/07/15 22:28, Joel Rosdahl wrote:
(Sorry for the delayed reply, I have been on vacation.)
No problem; me too!
No no, doing an extra read of initial data is not needed. If something I
wrote implied that I must have been unclear.
OK, all clear now. I don't recall the exact code path for
(Resend since my original mail didn't reach the mailing list properly.)
(Sorry for the delayed reply, I have been on vacation.)
On cache-hit, there's currently no reason to actually look inside the file,
right? It just does the copy blind (I forget exactly how). Reading the
initial data from
] Caching failed compilations
On 06/07/15 21:44, Joel Rosdahl wrote:
That sounds like a reasonable idea, but I have occasionally seen empty
object files in large and busy caches (it could be due to filesystem
failure, hardware failure or hard system reset), so I'm afraid that
using zero-length
On 05/07/15 16:47, Joel Rosdahl wrote:
Hi,
I did have a look at how feasible it is, and basically I think it
can be done.
Yes, caching failures (from the compiler, not the preprocessor) would be
feasible and I think that it's a good idea, at least as an optional feature.
I'm not very
After thinking further, I'd be tempted to say that ccache should *not*
cache failures with exit codes other than 1 as they're likely not
repeatable (OOM, Crtl-C, etc.).
Perhaps just signal a failed compile with a cache result that is present
but zero-length? (We could also say that it
Hi,
I did have a look at how feasible it is, and basically I think it can be
done.
Yes, caching failures (from the compiler, not the preprocessor) would be
feasible and I think that it's a good idea, at least as an optional feature.
I'm not very tempted to add a new kind of file for storing
On 30/06/15 15:30, Akim Demaille wrote:
Could ccache offer a mode where even failed compiled be ccached?
I'd like to see this too!
Or rather, I would have liked to see this on a project I worked on a
while ago. It's not really a common use case for most people, I'd
imagine, and not
