cache misses slower, though, so it is better to find and fix the root cause.
-ERRONEOUS OBJECT FILES
-~~~~~~~~~~~~~~~~~~~~~~
-
-There are no reported issues about ccache producing broken object files. That
-doesn't mean it can't happen, so if you find a repeatable case, please report
-it.
-
-That said, it should be noted that ccache is susceptible to general storage
-problems. If a bad object file sneaks into the cache for some reason, it will
-of course stay bad. Some possible reasons for erroneous object files are bad
-hardware (disk drive, disk controller, memory, etc), buggy drivers or file
-systems, a bad *CCACHE_PREFIX* command or compiler wrapper. If this happens,
-you can either find out which object file is broken by reading the debug log
-and then delete the bad object file from the cache, or you can simply clear the
-whole cache with *ccache -C* if you don't mind losing other cached results.
+CORRUPT OBJECT FILES
+~~~~~~~~~~~~~~~~~~~~
+
+It should be noted that ccache is susceptible to general storage problems. If a
+bad object file sneaks into the cache for some reason, it will of course stay
+bad. Some possible reasons for erroneous object files are bad hardware (disk
+drive, disk controller, memory, etc), buggy drivers or file systems, a bad
+*CCACHE_PREFIX* command or compiler wrapper. If this happens, you can either
+find out which object file is broken by reading the debug log and then delete
+the bad object file from the cache, or you can simply clear the whole cache
+with *ccache -C* if you don't mind losing other cached results.
+
+There are no reported issues about ccache producing broken object files
+reproducibly. That doesn't mean it can't happen, so if you find a repeatable
+case, please report it.
MORE INFORMATION