From: Junio C Hamano <gitster@pobox.com>
To: Nicolas Pitre <nico@cam.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>, git@vger.kernel.org
Subject: Re: [PATCH] block-sha1: more good unaligned memory access candidates
Date: Thu, 13 Aug 2009 12:33:57 -0700 [thread overview]
Message-ID: <7v63crbja2.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: alpine.LFD.2.00.0908131304520.10633@xanadu.home
Nicolas Pitre <nico@cam.org> writes:
> As it is now, I was about to suggest:
>
> git mv block-sha1/sha1.[ch] .
> rmdir block-sha1
> rm -r mozilla-sha1
> rm -r arm
> rm -r ppc
>
> and remove support for openssl's SHA1 usage, making this implementation
> unconditional. After all it is faster, or so close to be faster than
> the alternatives, that we should probably cut on the extra dependency
> and simplify portability issues at the same time.
Wow. Is it now faster than the arm/ and ppc/ hand-tweaked assembly?
next prev parent reply other threads:[~2009-08-13 19:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 4:29 [PATCH] block-sha1: more good unaligned memory access candidates Nicolas Pitre
2009-08-13 16:45 ` Linus Torvalds
2009-08-13 17:23 ` Nicolas Pitre
2009-08-13 19:33 ` Junio C Hamano [this message]
2009-08-13 19:54 ` Linus Torvalds
2009-08-13 20:13 ` Nicolas Pitre
2009-08-14 22:52 ` [PATCH] block-sha1/sha1.c: silence compiler complaints by casting void* to uintptr_t Brandon Casey
2009-08-15 0:08 ` Johannes Schindelin
2009-08-15 0:19 ` Linus Torvalds
2009-08-15 0:44 ` Brandon Casey
2009-08-15 1:46 ` Junio C Hamano
2009-08-15 2:34 ` Brandon Casey
2009-08-15 3:16 ` Junio C Hamano
2009-08-15 18:43 ` Linus Torvalds
2009-08-15 0:52 ` Brandon Casey
-- strict thread matches above, loose matches on Subject: below --
2009-08-13 20:15 [PATCH] block-sha1: more good unaligned memory access candidates George Spelvin
2009-08-13 21:28 ` Nicolas Pitre
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=7v63crbja2.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
--cc=torvalds@linux-foundation.org \
/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