> > There might be a subtle issue with ccache assuming that the compiler > > that created a cache-hit object did not change. I'm only aware of > > ccache verifying compiler versions (string compare) in the > > hit-check, which alone doesn't suffice to guarantee that the cache > > is (or should be) hit. > > No, it records the timestamp of the compiler driver. These would > always be different in a bootstrap run, so you would never get any > cache hits for second and third stage object files.
Ah, wasn't sure that it did that, but thanks for pointing that out. Bummer. "No ccache for you!!!" Fang
