Sam Russell wrote: > > Bug: code reads one more word from memory than it should. > > This is a good idea. The nice thing with CRC its that it's pseudo-random so > having the extra trailing randomb bytes helps us catch this but also even > uninitialised memory at the end of the string is going to make the tests > fail if we read more than requested. We also have 0-length reads in the mix > which is a no-op and returns 0x00000000 as a result.
That's not what I mean. I mean: Reading one word too much from memory into a register and then ending up not using it. This is a classical mistake that can happen when doing loop unrolling, especially when combined with doing memory fetches early (to avoid latencies). Bruno
