GNU bug report logs - #72588
performance bug regarding CRC32 algorithm implementation

Previous Next

Package: gzip;

Reported by: Daniel Ruf <ruf.shagentur <at> googlemail.com>

Date: Mon, 12 Aug 2024 06:53:01 UTC

Severity: normal

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

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

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

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-gzip <at> gnu.org:
bug#72588; Package gzip. (Mon, 12 Aug 2024 06:53:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to Daniel Ruf <ruf.shagentur <at> googlemail.com>:
New bug report received and forwarded. Copy sent to bug-gzip <at> gnu.org. (Mon, 12 Aug 2024 06:53:02 GMT) Full text and rfc822 format available.

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

From: Daniel Ruf <ruf.shagentur <at> googlemail.com>
To: bug-gzip <at> gnu.org
Subject: performance bug regarding CRC32 algorithm implementation
Date: Mon, 12 Aug 2024 08:51:50 +0200

[Message part 1 (text/plain, inline)]
During my research regarding faster gzip implementations I found
https://medium.com/@techhara/speeding-up-system-gzip-by-60-75edbc8ac0e8

Is the article correct and the implementation should be updated, or is the
benchmark flawed?

[Message part 2 (text/html, inline)]
Information forwarded to bug-gzip <at> gnu.org:
bug#72588; Package gzip. (Fri, 16 Aug 2024 12:21:01 GMT) Full text and rfc822 format available.

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

From: p.z.l <p.z.l <at> o2.pl>
To: Daniel Ruf via "GNU gzip discussion and bug reports.
 <bug-gzip <at> gnu.org>, Daniel Ruf <ruf.shagentur <at> googlemail.com>,
 72588 <at> debbugs.gnu.org <72588 <at> debbugs.gnu.org>
Subject: Re: bug#72588: performance bug regarding CRC32 algorithm implementation
Date: Fri, 16 Aug 2024 09:36:39 +0200

[Message part 1 (text/plain, inline)]
Is the article correct and the implementation should be updated, or is the  benchmark flawed?   I&#39;ll go classic - it&#39;s not a bug it&#39;s a feature.   lists.gnu.org https://lists.gnu.org/archive/html/bug-gzip/2023-11/msg00000.html

[Message part 2 (text/html, inline)]
Information forwarded to bug-gzip <at> gnu.org:
bug#72588; Package gzip. (Fri, 16 Aug 2024 12:21:03 GMT) Full text and rfc822 format available.
Reply sent to Paul Eggert <eggert <at> cs.ucla.edu>:
You have taken responsibility. (Tue, 11 Feb 2025 07:53:02 GMT) Full text and rfc822 format available.
Notification sent to Daniel Ruf <ruf.shagentur <at> googlemail.com>:
bug acknowledged by developer. (Tue, 11 Feb 2025 07:53:02 GMT) Full text and rfc822 format available.

Message #16 received at 72588-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Daniel Ruf <ruf.shagentur <at> googlemail.com>
Cc: 72588-done <at> debbugs.gnu.org
Subject: Fwd: Re: performance bug regarding CRC32 algorithm implementation
Date: Mon, 10 Feb 2025 23:52:02 -0800

[Message part 1 (text/plain, inline)]
[Resending because my earlier email had the wrong bug number.]

Due to work by Sam Russell and others it looks like gzip now has faster 
CRC32 code on Savannah master, so closing this old bug report. See:

https://bugs.gnu.org/74927
https://bugs.gnu.org/74192
[Re: performance bug regarding CRC32 algorithm implementation.eml (message/rfc822, attachment)]
bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Tue, 11 Mar 2025 11:24:20 GMT) Full text and rfc822 format available.
This bug report was last modified 121 days ago.

Previous Next

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