GNU bug report logs - #21693
[PATCH] doc: remove obsolete performance comment

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 21693 in the body.
You can then email your comments to 21693 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: bug-coreutils <at> gnu.org
Cc: Paul Eggert <eggert <at> cs.ucla.edu>
Subject: [PATCH] doc: remove obsolete performance comment
Date: Fri, 16 Oct 2015 12:08:33 -0700

sha512sum can be faster than sha256sum.
E.g., ‘dd if=/dev/zero bs=1024k count=1024 | time sha256sum’
reports 8.16 user CPU seconds on my host, whereas sha512sum
consumes 5.45 seconds (Fedora x86-64 on an AMD Phenom II X4 910e).
Although sha512sum is still considerably slower on x86, a good
chunk of uses are on 64-bit hosts and anyway there’s little point
to scaring people away from sha512sum nowadays.
* doc/coreutils.texi (sha2 utilities): Remove obsolete comment.
---
 doc/coreutils.texi | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index a029ec6..c988aca 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -3948,9 +3948,6 @@ these commands are precisely the same as for @command{md5sum}
 and @command{sha1sum}.
 @xref{md5sum invocation}.
 
-Note: The SHA384 and SHA512 digests are considerably slower to
-compute, especially on 32-bit computers, than SHA224 or SHA256.
-
 
 @node Operating on sorted files
 @chapter Operating on sorted files
-- 
2.1.0

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.