| To: | Franck Bui-Huu <vagabon.xyz@gmail.com> |
|---|---|
| Subject: | Re: [RFC] Add __initbss section |
| From: | "Maciej W. Rozycki" <macro@linux-mips.org> |
| Date: | Tue, 16 Oct 2007 11:29:50 +0100 (BST) |
| Cc: | Ralf Baechle <ralf@linux-mips.org>, Geert Uytterhoeven <geert@linux-m68k.org>, linux-mips <linux-mips@linux-mips.org> |
| In-reply-to: | <4713C840.8080206@gmail.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <470DF25E.60009@gmail.com> <Pine.LNX.4.64N.0710111307180.16370@blysk.ds.pg.gda.pl> <4712738A.5000703@gmail.com> <Pine.LNX.4.64N.0710151311350.16262@blysk.ds.pg.gda.pl> <4713C840.8080206@gmail.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
On Mon, 15 Oct 2007, Franck Bui-Huu wrote:
> Well, since .init.bss is declared as follow:
>
> .init.bss (NOLOAD) : {
> ...
> }
>
> data should not take any space in the image...
The above only marks it as unloadable (cf. e.g. debugging information).
It is still there.
> I meant to be able to put data into .init.bss section from assembly
> code (*.S files) like __INITDATA does for .init.data section.
That does not differ from what has to be done for any other language --
ultimately `gas', which is responsible for such arrangements, has to see
an appropriate ".section" directive.
Maciej
|
| Previous by Date: | Re: [RFC] Add __initbss section, Franck Bui-Huu |
|---|---|
| Next by Date: | Re: [PATCH] mm/pg-r4k.c: Dump the generated code, Nigel Stephens |
| Previous by Thread: | Re: [RFC] Add __initbss section, Franck Bui-Huu |
| Next by Thread: | Re: [RFC] Add __initbss section, Franck Bui-Huu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |