[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080224090750.GB8169@uranus.ravnborg.org>
Date: Sun, 24 Feb 2008 10:07:50 +0100
From: Sam Ravnborg <sam@...nborg.org>
To: Samuel Tardieu <sam@...1149.net>
Cc: Andi Kleen <andi@...stfloor.org>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: Reducing debuginfo size by removing unneeded includes
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 ;-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists