From: Denys Vlasenko <vda.linux@googlemail.com>
To: David Howells <dhowells@redhat.com>
Cc: Michal Marek <mmarek@suse.cz>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
linux-arch@vger.kernel.org,
Parisc List <linux-parisc@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>, Tim Abbott <tabbott@ksplice.com>,
Tim Bird <tim.bird@am.sony.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Matt Fleming <matt@console-pimps.org>,
Arnd Bergmann <arnd@arndb.de>, Anders Kaseorg <andersk@mit.edu>,
Andi Kleen <andi@firstfloor.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH 2/4] module linker script: coalesce function and data sections
Date: Thu, 29 Jul 2010 03:24:36 +0200 [thread overview]
Message-ID: <201007290324.36745.vda.linux@googlemail.com> (raw)
In-Reply-To: <29025.1280363105@redhat.com>
On Thursday 29 July 2010 02:25, David Howells wrote:
> Denys Vlasenko <vda.linux@googlemail.com> wrote:
>
> > + .data 0 : AT(0) { *(.data .data.[A-Za-z0-9_$^]*) }
> > + .bss 0 : AT(0) { *(.bss .bss.[A-Za-z0-9_$^]*) }
>
> What about .sdata and .sbss sections produced by arches that support small
> data sections?
linker groups all similarly-named input sections into one output section
with the same name, if the name does not match any rule in the linker
script.
Basically, it should work as if there is a rule:
.sbss 0 : AT(0) { *(.sbss) }
--
vda
next prev parent reply other threads:[~2010-07-29 1:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 23:47 [PATCH 0/4] function/data-sections Denys Vlasenko
2010-07-28 23:47 ` [PATCH 1/4] modpost: support objects with more than 64k sections Denys Vlasenko
2010-07-28 23:47 ` [PATCH 2/4] module linker script: coalesce function and data sections Denys Vlasenko
2010-07-29 0:25 ` David Howells
2010-07-29 1:24 ` Denys Vlasenko [this message]
2010-07-29 9:09 ` David Howells
2010-08-03 13:47 ` Michal Marek
2010-08-06 2:18 ` Denys Vlasenko
2010-07-28 23:47 ` [PATCH 3/4] kernel linker stripts: accomodate " Denys Vlasenko
2010-07-28 23:47 ` [PATCH 4/4] boot " Denys Vlasenko
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=201007290324.36745.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=andersk@mit.edu \
--cc=andi@firstfloor.org \
--cc=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@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=sfr@canb.auug.org.au \
--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