Glibc change exposing bugs

Posted Nov 10, 2010 22:04 UTC (Wed) by joib (subscriber, #8541)
In reply to: Glibc change exposing bugs by MisterIO
Parent article: Glibc change exposing bugs

And, this has a couple of other nice advantages

1) Less I$ pollution. You won't see this in a memcpy() benchmark, but what about a more realistic workload?

2) Give some incentive to CPU makers to optimize the simple rep mov instead of requiring ever more fancy unrolled loops written in the latest instruction set extension. :)