On Sun, Mar 10, 2013 at 6:54 PM, Antoine Pelisse <apelisse@xxxxxxxxx> wrote: > On Sun, Mar 10, 2013 at 12:43 PM, Antoine Pelisse <apelisse@xxxxxxxxx> wrote: >> On Sun, Mar 10, 2013 at 11:38 AM, Duy Nguyen <pclouds@xxxxxxxxx> wrote: >>> glibc's C strncmp version does 4-byte comparison at a time when n >=4, >>> then fall back to 1-byte for the rest. >> >> Looking at this >> (http://fossies.org/dox/glibc-2.17/strncmp_8c_source.html), it's not >> exactly true. >> >> It would rather be while (n >= 4), manually unroll the loop. > > By the way, if we know the length of the string, we could use memcmp. > This one is allowed to compare 4-bytes at a time (he doesn't care > about end of string). This is true because the value of the length > parameter is no longer "at most". We still need to worry about access violation after NUL when two strings have different lengths. That could be avoided in this particular case, but I think it's too fragile. -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html