From: John Reiser <jreiser@bitwagon.com>
To: binutils@sourceware.org
Subject: Re: RFC: Add zlib source to src CVS resposity
Date: Sat, 30 Oct 2010 22:19:00 -0000 [thread overview]
Message-ID: <4CCC99E2.70901@bitwagon.com> (raw)
In-Reply-To: <AANLkTikYSxV51_452Wuqox6mQ3_QwNjzNkBgV=NzKk4f@mail.gmail.com>
On 10/30/2010, H.J. Lu wrote:
> Binutils can compress/decompress debug sections if zlib is available.
> I imported zlib from gcc source tree to binutils source tree. ...
Please consider using -DNO_GZIP in zlib version 1.2.5 (April 19, 2010)
from http://zlib.net/ . Compiling zlib with -DNO_GZIP forces adler32
as the checksum algorithm instead of crc32, and zlib streams for the
data format instead of gzip streams. adler32 is significantly faster,
less energy intensive, and several kilobytes smaller in static size
because it uses no CRC table. The cost is a loss of at most 0.023%
in detecting corruption.
--
John Reiser, jreiser@BitWagon.com
next prev parent reply other threads:[~2010-10-30 22:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 21:12 H.J. Lu
2010-10-30 22:19 ` John Reiser [this message]
2010-11-01 17:21 ` Nick Clifton
2010-11-01 17:23 ` Nathan Froyd
[not found] <AANLkTikYSxV51_452Wuqox6mQ3_QwNjzNkBgV=NzKk4f__16997.3676828251$1288473196$gmane$org@mail.gmail.com>
2010-10-30 21:37 ` Frank Ch. Eigler
2010-10-30 22:28 ` H.J. Lu
2010-10-31 18:42 ` Ian Lance Taylor
2010-10-31 18:58 ` H.J. Lu
2010-10-31 19:13 ` Ian Lance Taylor
2010-11-01 17:13 ` Nick Clifton
2010-11-01 17:19 ` Daniel Jacobowitz
2010-11-01 23:56 ` Alan Modra
2010-11-02 1:03 ` Christopher Faylor
2010-11-02 8:19 ` Nick Clifton
2010-11-02 13:22 ` Ian Lance Taylor
2010-11-09 14:19 ` Mike Frysinger
2010-11-02 10:46 ` Paolo Bonzini
2010-10-31 19:54 ` Weddington, Eric
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=4CCC99E2.70901@bitwagon.com \
--to=jreiser@bitwagon.com \
--cc=binutils@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).