[...]
> It seems memcmp() is returning false miscompare status. If I use a
> for(){buf1[i] != buf2[i]} loop to scan the two read buffers after the
> memcmp() check, I find that the buffers are, in fact, identical. Now
> what ????
Compiler used? memcmp() used? Machine?
Note that the latest egcs snapshots by default enable optimizations based
on the assumption that only pointers to the same type can create aliases
(this according to ANSI C). The in-kernel mem* functions break this
assumption big time, probably other implementations do so too...
Try -fno-strict-aliasing
-- Dr. Horst H. von Brand mailto:vonbrand@inf.utfsm.cl Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/