This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
RE: -femit-struct-debug-reduced/baseonly debug info
- From: Evgeny Gavrin <evgeny dot gavrin at hotmail dot com>
- To: Ian Lance Taylor <iant at google dot com>
- Cc: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
- Date: Tue, 18 Jun 2013 14:53:11 +0000
- Subject: RE: -femit-struct-debug-reduced/baseonly debug info
- References: <SNT138-W101227728C29F752BE4608E28C0 at phx dot gbl>,<CAKOQZ8yEqQuOX2rUgDS+R3STe=sJSzb+AShnbxfVJeG5cnFDdw at mail dot gmail dot com>
Quote from the documentations is not clear to me: "Emit debug information for struct-like types only when the base name of the compilation source file matches the base name of file in which the type was defined, unless the struct is a template or defined in a system header. "
As I understood, this'll store info only about static types and I'll loose info about inlining, for example, am I right?
And to extend the question:
I don't understand what means direct or indirect accessed structs? Ordinary or generic ones? Where I can read about it?
/*
With optimism,
Evgeny Gavrin
email : evgeny.gavrin@hotmail.com
*/
----------------------------------------
> Date: Tue, 18 Jun 2013 06:43:18 -0700
> Subject: Re: -femit-struct-debug-reduced/baseonly debug info
> From: iant@google.com
> To: evgeny.gavrin@hotmail.com
> CC: gcc-help@gcc.gnu.org
>
> On Tue, Jun 18, 2013 at 4:40 AM, Evgeny Gavrin
> <evgeny.gavrin@hotmail.com> wrote:
>>
>> I'm trying to reduce the amount of debug info in my binaries.
>>
>> What kind of debug info will I loose in case of using -femit-struct-debug-reduced or -femit-struct-debug-baseonly?
>> And what is still available?
>
> The GCC manual explains how those options work. I could repeat that
> documentation but that seems unhelpful. Perhaps it would help if you
> could explain what you don't understand about the documentation.
>
> Ian