From: Sam Ravnborg <sam@ravnborg.org>
To: Samuel Tardieu <sam@rfc1149.net>
Cc: Andi Kleen <andi@firstfloor.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: Reducing debuginfo size by removing unneeded includes
Date: Sun, 24 Feb 2008 10:07:50 +0100 [thread overview]
Message-ID: <20080224090750.GB8169@uranus.ravnborg.org> (raw)
In-Reply-To: <2008-02-24-09-25-19+trackit+sam@rfc1149.net>
On Sun, Feb 24, 2008 at 09:25:19AM +0100, Samuel Tardieu wrote:
> Andy> -feliminate-unused-debug-types -feliminate-unused-debug-symbols
> Andy> -feliminate-dwarf2-dups
>
> Sam> google did not turn up anything useful. Do you have a poiter to
> Sam> where these are described?
>
> >From GCC (svn) man page:
>
> -feliminate-unused-debug-symbols
> Produce debugging information in stabs format (if that is sup‐
> ported), for only symbols that are actually used.
>
> -feliminate-unused-debug-types
> Normally, when producing DWARF2 output, GCC will emit debugging
> information for all types declared in a compilation unit, regard‐
> less of whether or not they are actually used in that compilation
> unit. Sometimes this is useful, such as if, in the debugger, you
> want to cast a value to a type that is not actually used in your
> program (but is declared). More often, however, this results in a
> significant amount of wasted space. With this option, GCC will
> avoid producing debug symbol output for types that are nowhere used
> in the source file being compiled.
>
> -feliminate-dwarf2-dups
> Compress DWARF2 debugging information by eliminating duplicated
> information about each symbol. This option only makes sense when
> generating DWARF2 debugging information with -gdwarf-2.
>
Hi Sam.
I did not include the '-f' part in my google search. When I did so I got more hits.
Thanks,
Sam - who is not talking to himself ;-)
next prev parent reply other threads:[~2008-02-24 9:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 23:03 Arnaldo Carvalho de Melo
2008-02-17 14:00 ` Thomas Gleixner
2008-02-18 5:12 ` Ingo Molnar
2008-02-18 13:12 ` Andi Kleen
2008-02-18 13:41 ` Arnaldo Carvalho de Melo
2008-02-18 14:50 ` Andi Kleen
2008-02-18 14:22 ` Arnaldo Carvalho de Melo
2008-02-18 14:01 ` Sam Ravnborg
2008-02-24 7:58 ` Sam Ravnborg
2008-02-24 8:25 ` Samuel Tardieu
2008-02-24 9:07 ` Sam Ravnborg [this message]
2008-02-24 12:23 ` Andi Kleen
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=20080224090750.GB8169@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=acme@redhat.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@rfc1149.net \
/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
all inboxes | Powered by JetHome®