Re: [RFC/PATCH] ignore memcmp() overreading in bsearch() callback

Johannes Schindelin [off-list ref] writes:

On Mon, 14 Jan 2013, Junio C Hamano wrote:

quoted

It appears that memcmp() uses the usual "one word at a time"
comparison and triggers valgrind in a callback of bsearch() used in
the refname search.  I can easily trigger problems in any script
with test_commit (e.g. "sh t0101-at-syntax.sh --valgrind -i -v")
without this suppression.

I have no way to replicate that issue, but I take your word for it. With
that in mind, here is my ACK.

Thanks.