From: Andi Kleen <andi@firstfloor.org>
To: Sam Ravnborg <sam@ravnborg.org>
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 13:23:35 +0100 [thread overview]
Message-ID: <20080224122335.GB13637@one.firstfloor.org> (raw)
In-Reply-To: <20080224075821.GA7781@uranus.ravnborg.org>
> > Just FYI, newer gcc does this in theory automatically when you specify
> >
> > -feliminate-unused-debug-types -feliminate-unused-debug-symbols
> google did not turn up anything useful.
> Do you have a poiter to where these are described?
info gcc
>
>
> > There is also -feliminate-dwarf2-dups, but it seems to even increase
> > obj dir size. Also -feliminate-dwarf2-dups seems to generate a lot of
>
> Google only turned up a patch from Mark Mitchell removing this
> in ~2001 timeframe.
> So again a pointer would be nice.
>
> I use FC8:
> gcc --version
> gcc (GCC) 4.1.2 20070925 (Red Hat 4.1.2-33)
>
> So this is far behind trunk that you use - but I have not had any
> real incentive to upgrade.
It's in my info pages for SUSE gcc 4.1. I didn't think it was
a SUSE extension though.
I also checked and all options are in gcc head and in gcc 4.3
>
> I would like to have a remote understanding of the options before
> enabling them.
Right now they are not useful to enable because they don't save
file size and in some cases make it even worse. I checked with some gcc
developers and they explained why that is so. gcc would need to be fixed first.
-Andi
prev parent reply other threads:[~2008-02-24 12:23 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
2008-02-24 12:23 ` Andi Kleen [this message]
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=20080224122335.GB13637@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
/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®