From: Doug Evans <dje@google.com>
To: Cary Coutant <ccoutant@google.com>
Cc: David Taylor <dtaylor@emc.com>, nick clifton <nickc@redhat.com>,
Binutils <binutils@sourceware.org>, gcc <gcc@gcc.gnu.org>,
gdb <gdb@sourceware.org>
Subject: Re: stabs support in binutils, gcc, and gdb
Date: Mon, 14 Jan 2013 16:12:00 -0000 [thread overview]
Message-ID: <CADPb22S9qHdGGPW-5-cK_cDESWVRSJfGgeWdyOAyw_rtGitkFA@mail.gmail.com> (raw)
In-Reply-To: <CAHACq4qW8iTdNN6GuuyqkZuFtLeh59wa91PmnNExiFbJB1Cq5Q@mail.gmail.com>
On Fri, Jan 11, 2013 at 6:55 PM, Cary Coutant <ccoutant@google.com> wrote:
>>> If I use objcopy --compress-debug-sections to compress the DWARF debug
>>> info (but don't use it on the STABS debug info), then the file size
>>> ratio is 3.4.
>>>
>>> While 3.4 is certainly better than 11.5, unless I can come up with a
>>> solution where the ratio is less than 2, I'm not currently planning on
>>> trying to convince them to switch to DWARF.
>>
>> The 3.4 number is the number I was interested in.
>> Thanks for computing it.
>
> It's not really fair to compare compressed DWARF with uncompressed stabs, is it?
Data is data.
Plus I doubt anyone is going to go to the trouble of compressing stabs.
Not that I think it's a priori worth the effort to dig deeper, but for
another datapoint, Redhat added an lza-compressed mini-dwarf-debug
section. I'm not sure what it supports (if anything beyond making
backtraces better).
next prev parent reply other threads:[~2013-01-14 16:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 16:22 David Taylor
2013-01-03 16:42 ` Richard Biener
2013-01-03 16:53 ` Joel Brobecker
2013-01-03 16:56 ` nick clifton
2013-01-04 3:31 ` Doug Evans
2013-01-11 14:53 ` David Taylor
2013-01-11 17:41 ` Doug Evans
2013-01-12 1:55 ` Cary Coutant
2013-01-12 2:17 ` Ian Lance Taylor
2013-01-14 16:06 ` Doug Evans
2013-01-14 19:45 ` Cary Coutant
2013-01-14 16:12 ` Doug Evans [this message]
2013-01-14 19:49 ` Jan Kratochvil
2013-01-12 13:26 ` Andreas Schwab
2013-01-14 18:57 ` David Taylor
2013-01-14 22:18 ` Andreas Schwab
2013-01-14 23:41 ` Eric Botcazou
[not found] <12972.1357230104__33958.3243280233$1357230256$gmane$org@usendtaylorx2l>
2013-01-03 17:02 ` Tom Tromey
2013-01-03 20:53 ` David Edelsohn
2013-01-03 21:53 ` Jonas Maebe
2013-01-03 22:02 ` David Edelsohn
2013-01-04 4:12 ` Joel Brobecker
2013-01-04 20:20 ` David Edelsohn
2013-01-05 0:11 ` David Edelsohn
2013-01-05 7:53 ` Joel Brobecker
2013-01-05 13:28 ` David Edelsohn
2013-01-05 14:52 ` Joel Brobecker
2013-01-06 0:26 ` David Edelsohn
2013-01-06 7:00 ` Joel Brobecker
2013-01-08 8:10 ` Joel Brobecker
2013-01-08 14:38 ` David Edelsohn
2013-01-08 14:46 ` Arnaud Charlet
2013-01-08 14:49 ` David Edelsohn
2013-01-08 14:58 ` Arnaud Charlet
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=CADPb22S9qHdGGPW-5-cK_cDESWVRSJfGgeWdyOAyw_rtGitkFA@mail.gmail.com \
--to=dje@google.com \
--cc=binutils@sourceware.org \
--cc=ccoutant@google.com \
--cc=dtaylor@emc.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=nickc@redhat.com \
/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).