From: Ralf Baechle <ralf@linux-mips.org>
To: Manuel Lauss <mano@roarinelk.homelinux.net>
Cc: linux-mips@linux-mips.org
Subject: Re: 2.6.26-gitX: insane number of section headers
Date: Wed, 16 Jul 2008 11:59:27 +0100 [thread overview]
Message-ID: <20080716105927.GA8206@linux-mips.org> (raw)
In-Reply-To: <20080716081532.GB3184@roarinelk.homelinux.net>
On Wed, Jul 16, 2008 at 10:15:32AM +0200, Manuel Lauss wrote:
> On Wed, Jul 16, 2008 at 09:52:46AM +0200, Manuel Lauss wrote:
> > Hello,
> >
> > Todays 2.6.26-git kernel produces an insane amout of section headers in the
> > vmlinux file, one for every function. Is that intentional, or a toolchain
> > problem on my side (binutils-2.18, gcc-4.2.4)?
>
> I see Ralf added -ffunction-sections with commit
> 372a775f50347f5c1dd87752b16e5c05ea965790.
I consider that an experimental commit. It's meant to solve the problems
we're having on a few very large compilation units with the limited length
of branches. But if the cure turns out to be worse than the illness I'm
ready to pull it again.
A more proper patchset should modify the linker scripts to avoid the
excessive large number of sections you've noticed. Somebody else is
currently working on a patchset to allow the --gc-sections ld option so
I decieded to take the path of least resistance for now.
Ralf
next prev parent reply other threads:[~2008-07-16 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 7:52 2.6.26-gitX: insane number of section headers Manuel Lauss
2008-07-16 8:15 ` Manuel Lauss
2008-07-16 10:59 ` Ralf Baechle [this message]
2008-07-16 11:03 ` Manuel Lauss
2008-07-16 11:08 ` Ralf Baechle
2008-07-16 11:28 ` Manuel Lauss
2008-07-24 10:03 ` Atsushi Nemoto
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=20080716105927.GA8206@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=mano@roarinelk.homelinux.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