| 1 |
On Thu, 29 Apr 2010 09:48:28 +0200 |
| 2 |
"Paweł Hajdan, Jr." <phajdan.jr@g.o> wrote: |
| 3 |
> > ccache itself hasn't been the problem, but unreliable hardware has. |
| 4 |
> > Provably by removing the corrupt cache files, then running with |
| 5 |
> > ccache a few more times, and having everything work perfectly. |
| 6 |
> |
| 7 |
> I see. However, I'd consider not detecting the corruption a bug. |
| 8 |
|
| 9 |
gcc also doesn't detect most hardware faults. Nor does glibc. Nor does |
| 10 |
the kernel. There's very little software out there that's designed to |
| 11 |
run correctly even on broken hardware, and the little that there is is |
| 12 |
mostly keeping planes flying. |
| 13 |
|
| 14 |
-- |
| 15 |
Ciaran McCreesh |
Archives