From: Taylor Blau <me@ttaylorr.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Taylor Blau <me@ttaylorr.com>
Subject: Re: [PATCH] block-sha1: remove use of assembly
Date: Mon, 7 Mar 2022 18:32:42 -0500 [thread overview]
Message-ID: <YiaWGrBNuk1+j89z@nand.local> (raw)
In-Reply-To: <20220307232552.2799122-1-sandals@crustytoothpaste.net>
On Mon, Mar 07, 2022 at 11:25:52PM +0000, brian m. carlson wrote:
> In the block SHA-1 code, we have special assembly code for i386 and
> amd64 to perform rotations with assembly. This is supposed to help pick
> the correct rotation operation depending on which rotation is smaller,
> which can help some systems perform slightly better, since any circular
> rotation can be specified as either a rotate left or a rotate right.
> However, this isn't needed, so we should remove it.
At -O1 or higher (at least on GCC) this optimization is indeed
performed. Here's a Godbolt example that shows this:
https://godbolt.org/z/9zMP93hr1
so I agree that this code isn't helping us at all. And in the
meantime...
> The downside of using this code, however, is that it uses a GCC
> extension, which makes the compiler complain when using -pedantic unless
> it's prefixed with __extension__. We could fix that, but since it's
> not needed, let's just remove it. We haven't noticed this because
> almost everyone uses the SHA1DC code instead, but it still shows up for
> some people.
...it makes it impossible to compile git if you have
`BLK_SHA1=YesPlease` and `DEVELOPER=1` in your environment. So I am
happy to see this go.
On another note: missing Signed-off-by?
Thanks,
Taylor
next prev parent reply other threads:[~2022-03-07 23:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 23:25 [PATCH] block-sha1: remove use of assembly brian m. carlson
2022-03-07 23:32 ` Taylor Blau [this message]
2022-03-08 2:20 ` brian m. carlson
2022-03-08 2:22 ` [PATCH v2] " brian m. carlson
2022-03-08 13:38 ` Ævar Arnfjörð Bjarmason
2022-03-09 22:10 ` brian m. carlson
2022-03-09 22:32 ` Taylor Blau
2022-03-09 23:52 ` Ævar Arnfjörð Bjarmason
2022-03-10 1:59 ` Carlo Marcelo Arenas Belón
2022-03-10 2:34 ` Taylor Blau
2022-03-10 17:47 ` [PATCH v3] block-sha1: remove use of obsolete x86 assembly brian m. carlson
2022-03-10 19:18 ` Junio C Hamano
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=YiaWGrBNuk1+j89z@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sandals@crustytoothpaste.net \
/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).