From: "René Scharfe" <l.s.r@web.de>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] fast-import: use hashcmp() for SHA1 hash comparison
Date: Fri, 18 Jul 2014 21:14:05 +0200 [thread overview]
Message-ID: <53C971FD.6040500@web.de> (raw)
In-Reply-To: <20140718184246.GS12427@google.com>
Am 18.07.2014 20:42, schrieb Jonathan Nieder:
> René Scharfe wrote:
>
>> Signed-off-by: Rene Scharfe <l.s.r@web.de>
>> ---
>> fast-import.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Before:
>
> $ size git-fast-import
> text data bss dec hex filename
> 804138 6768 754160 1565066 17e18a git-fast-import
>
> After:
>
> $ size git-fast-import
> text data bss dec hex filename
> 804154 6768 754160 1565082 17e19a git-fast-import
>
> So this makes the text size worse on this machine (amd64, building
> with gcc 4.8.2 -O2). That's probably because the old code does 'call
> memcmp', while the new code inlines it. Inlining is presumably the
> better choice.
>
> More importantly, the new code is more readable.
Yes, the latter point is the important one.
If inlining is really better is another matter; I don't understand how
1a812f3a (hashcmp(): inline memcmp() by hand to optimize) could have
made git gc 18% faster, as it claimed. I would expect memcmp(), which
can compare more than a byte at a time, to be significantly faster -- or
at least just as fast as whatever the compiler does with the inlined
version.
René
next prev parent reply other threads:[~2014-07-18 19:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 16:00 [PATCH] fast-import: use hashcmp() for SHA1 hash comparison René Scharfe
2014-07-18 18:42 ` Jonathan Nieder
2014-07-18 19:14 ` René Scharfe [this message]
2014-07-18 23:57 ` Jeff King
2014-07-19 12:11 ` René Scharfe
2014-07-19 16:43 ` brian m. carlson
2014-07-19 17:53 ` René Scharfe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53C971FD.6040500@web.de \
--to=l.s.r@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).