> > Sounds reasonable to me, although it looks like GCC's old builtin > > memcmp expansion actually failed to implement our specification: it > > returns -1, 0, or +1, like your patch, rather than the difference of > > the first differing bytes or zero as our man page specifies. For most > > uses it doesn't matter, of course, but we ought to make sure to follow > > our own specification. > > memcmp is only supposed to provide the correct sign, not the difference.
true, but that's not what memcmp(9) says. however, unless we have a good reason, i think we should change our docs to fit. .mrg.
