From: Tom Tromey <tromey@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: Project Archer <archer@sourceware.org>, Jakub Jelinek <jakub@redhat.com>
Subject: Re: Fedora 14 debug proposal
Date: Tue, 15 Jun 2010 19:46:00 -0000 [thread overview]
Message-ID: <m38w6gulji.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100613104010.6D1174077C@magilla.sf.frob.com> (Roland McGrath's message of "Sun, 13 Jun 2010 03:40:10 -0700 (PDT)")
>>>>> "Roland" == Roland McGrath <roland@redhat.com> writes:
Roland> For Fedora purposes, dropping .debug_pub* sections could just as
Roland> well be done in the stripping stage. And, I don't think they
Roland> really cost much space in the grand scheme of things. So there
Roland> is little real motivation to fiddle gcc at all until after we
Roland> have completed basically everything else in the related realms.
Doing it in gcc can save some space, by not putting useless stuff into
the string table. I didn't try to measure this. Just stripping the
sections does not save much space, as you hypothesized; I did a test
with objcopy on all the debuginfo I have currently installed (OO.o plus
other random bits):
opsy. du -s debug stripped
1883432 debug
1812156 stripped
71276 savings
The indices are about 3x the size of the savings:
opsy. du -s Out
208876 Out
Tom> 3. If we are shipping GCC 4.5 in F14, I think we should enable the
Tom> .debug_types stuff by default. This will shrink debuginfo and it
Tom> makes gdb use less memory.
Roland> libdw does not yet handle .debug_types. It of course will, but
Roland> I wouldn't like to have a gcc defaults change on any queue until
Roland> we are quite concrete with getting all the support in line.
Yeah, that would be good for us too; some of the recent gcc changes
caught us by surprise. OTOH I don't want to stop Jakub's gusto, maybe
just get a little more warning of coming gdb-impacting changes.
Tom> This one is optional, in particular I assume it will be subsumed by
Tom> the other DWARF compression work.
Roland> It should be, yes. I don't see any reason that .debug_types and
Roland> DW_FORM_ref_sig8 need to survive final linking. The normal reference
Roland> forms are more efficient for consumers to use.
Why is that? I looked at the gdb code here and nothing really stood out.
Tom
next prev parent reply other threads:[~2010-06-15 19:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 20:38 Tom Tromey
2010-06-09 13:54 ` Dodji Seketeli
2010-06-09 16:11 ` Tom Tromey
2010-06-11 20:31 ` Tom Tromey
2010-06-14 10:17 ` Jakub Jelinek
2010-06-11 20:39 ` Tom Tromey
2010-06-11 20:33 ` Tom Tromey
2010-06-13 10:40 ` Roland McGrath
2010-06-14 20:06 ` Tom Tromey
2010-06-15 19:46 ` Tom Tromey [this message]
2010-06-15 22:26 ` Roland McGrath
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=m38w6gulji.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@sourceware.org \
--cc=jakub@redhat.com \
--cc=roland@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).