From: Denys Vlasenko <vda.linux@googlemail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Tim Abbott <tabbott@ksplice.com>, Tim Bird <tim.bird@am.sony.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-kernel@vger.kernel.org,
Matt Fleming <matt@console-pimps.org>,
linux-arch@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Michal Marek <mmarek@suse.cz>,
Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: Testing of function/data-sections on linux-2.6.35-rc4
Date: Mon, 26 Jul 2010 03:31:34 +0200 [thread overview]
Message-ID: <201007260331.34372.vda.linux@googlemail.com> (raw)
In-Reply-To: <20100723203543.GB27288@merkur.ravnborg.org>
Hi Sam,
On Friday 23 July 2010 22:35, Sam Ravnborg wrote:
> >
> > Then, in order to also garbage-collect the sections, I added
> >
> > LDFLAGS_vmlinux += --gc-sections
> >
> > in top-level Makefile.
> >
> > This requires the additional patch (linux-2.6.35-rc4-fsgs.patch)
> > which adds KEEP(section) directives to kernel linker stripts.
> > Otherwise, linker will discard some crucial sections.
> >
>
> Changelog does not address why you need:
>
> -Map $@.ldmap
>
> and what effect they have.
I didn't plan to push the last step (--gc-sections) to mainline yet.
Thus the patch has debugging stuff in it.
> And it is obvious that some archs should consolidate a little more from
> asm-generic/vmlinux.lds.h.
> But that said this patch looks much better than the initial versions posted.
>
> How do you determine which sections needs the KEEP()?
> Worth documenting for future when we add new sections.
No problem, I will be adding comments at every KEEP() why it's needed.
--
vda
next prev parent reply other threads:[~2010-07-26 1:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-18 15:03 Testing of function/data-sections on linux-2.6.35-rc4 Denys Vlasenko
2010-07-18 18:24 ` Geert Uytterhoeven
2010-07-18 23:31 ` Denys Vlasenko
2010-07-23 19:10 ` Sam Ravnborg
2010-07-26 0:52 ` Denys Vlasenko
2010-07-26 7:23 ` Sam Ravnborg
2010-07-23 20:24 ` Sam Ravnborg
2010-07-26 1:29 ` Denys Vlasenko
2010-07-26 7:27 ` Sam Ravnborg
2010-07-23 20:29 ` Sam Ravnborg
2010-07-23 20:35 ` Sam Ravnborg
2010-07-26 1:31 ` Denys Vlasenko [this message]
2010-07-26 7:28 ` Sam Ravnborg
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=201007260331.34372.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.org \
--cc=tabbott@ksplice.com \
--cc=tim.bird@am.sony.com \
/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