Dan Jacobson [EMAIL PROTECTED] wrote:
Alfred It is so inflexible because you haven't bothered sending a patch.
I see. So you all think the concept is great, and doesn't violate any
standards, etc., so all that is left is writing the code. I will not
regret writing the code as the concept
at http://arctic.org/~dean/crypto/sha1.html you'll find a coreutils
patch which includes a new implementation of SHA1 using SSE2 hardware for
a speedup ranging from 1.2x to 1.9x depending on which SSE2-capable CPU is
used.
there's a complication to compiling this code -- it requires the intel
Matt Weinstein [EMAIL PROTECTED] writes:
Problem:
sum does not output the filename of the file being sum(med) if only one
filename is supplied.
This could lead to problems with e.g. archiving systems, etc.
This is inconsistent and undocumented to the best of my knowledge.
It is at least
dean gaudet [EMAIL PROTECTED] writes:
at http://arctic.org/~dean/crypto/sha1.html you'll find a coreutils
patch which includes a new implementation of SHA1 using SSE2 hardware for
a speedup ranging from 1.2x to 1.9x depending on which SSE2-capable CPU is
used.
there's a complication to
