linux-mips
[Top] [All Lists]

Re: [RFC] Add __initbss section

To: "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [RFC] Add __initbss section
From: Franck Bui-Huu <vagabon.xyz@gmail.com>
Date: Mon, 15 Oct 2007 22:06:24 +0200
Cc: Ralf Baechle <ralf@linux-mips.org>, Geert Uytterhoeven <geert@linux-m68k.org>, linux-mips <linux-mips@linux-mips.org>
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=oKdYBCPtTrHmuCzka+Wi2GAT3LB1CbLgEtQSkuaMddY=; b=aH5agP1DX4dUxBw8REGtA+49/m/ZS6wr6qXZtKU+ZOcSxUvCH07/n16+wPs3b2nYB+H0z7GDmk2OQfGOKPz7SvKO7ECorQZYUEsMQ/0mHDRmF6O1mcZju3mOqkmgaD0NY/13cT4OfmtDgs/hbYJaPcRfT0QCqIPgHyna/4dSu58=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=Se6w1K71fNsEHw1EPdIT2WisY5AdA78CjHEkLgB1bFcSY9AAIzXrxcfpUqsQHTAcQgD2TXOpJy9mqvRvD0S8c5hqfcGv2WYYwFI9EIZdrehU/MdQnz6nz+/87eiM/iHkvTsZjBqSGtscDzyX2Hd+/4jSxYl4PMdXDgNnJKXmUXY=
In-reply-to: <Pine.LNX.4.64N.0710151311350.16262@blysk.ds.pg.gda.pl>
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>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Thunderbird 2.0.0.5 (X11/20070719)
Maciej W. Rozycki wrote:
> On Sun, 14 Oct 2007, Franck Bui-Huu wrote:
> 
>>>  I guess for a bss-type section you want to use something like:
>>>
>>>     .section .init.bss,"aw",@nobits
>>>
>> Sorry but I'm missing your point here. This indeed should be added
>> for assembler code but I don't see how it's related with the kernel
>> image size difference I was seeing.
> 
>  Well, otherwise the section is marked as containing data and therefore 
> taking space in the image.

Well, since .init.bss is declared as follow:

        .init.bss (NOLOAD) : {
                ...
        }

data should not take any space in the image...

> 
>  What do you mean by "assembler code" in this context, BTW?

I meant to be able to put data into .init.bss section from assembly
code (*.S files) like __INITDATA does for .init.data section.

                Franck

<Prev in Thread] Current Thread [Next in Thread>