From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-mips <linux-mips@linux-mips.org>
Subject: Re: [RFC] Add __initbss section
Date: Sun, 14 Oct 2007 21:42:08 +0200 [thread overview]
Message-ID: <47127110.4060206@gmail.com> (raw)
In-Reply-To: <20071011124410.GA17202@linux-mips.org>
Ralf Baechle wrote:
> On Thu, Oct 11, 2007 at 11:52:30AM +0200, Franck Bui-Huu wrote:
>
>> Other question: I noticed that the exit.data section is not
>> discarded. Could anybody give me the reason why ?
>
> .exit.data and .exit.text may reference each other. __exit functions
> generally get compiled into .exit.text but some constructs such as jump
> tables for switch() constructs may be compiled into address tables which
> gcc unfortunately will put into .rodata, so .rodata will end up
> referencing function addresses in .exit.text which makes ld unhappy if
> .exit.text was discarded. So until this is fixed in gcc we can't
> discard exit code, unfortunately.
>
Thanks for the details.
I actually don't see any point to move these tables in .rodata since
they're part of the code...
> It's actually an issue which doesn't strike very often, so users who are
> desparate for shrinking the kernel down could try to undo patchsets:
>
> 6f0b1e5d266fb1d0da019c07b56ccc02c3a4f53a
> ca7402fed2a76cd5a417ac4d375a5539dcb2b6de
>
> and see if they can get away with it. If the final kernel link succeeds,
> the build would be ok.
>
> I think gcc should probably put the jump table into a .subsection if
> a section was explicitly requested, at least for non-PIC code.
>
yes that would be great, and do the same for strings, data and we could
get rid of all __initxxx annotations.
Franck
next prev parent reply other threads:[~2007-10-14 19:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 9:52 [RFC] Add __initbss section Franck Bui-Huu
2007-10-11 9:54 ` [PATCH 1/2] Add .init.bss section Franck Bui-Huu
2007-10-11 9:58 ` [PATCH 2/2] Add .init.bss section for MIPS Franck Bui-Huu
2007-10-11 12:44 ` [RFC] Add __initbss section Ralf Baechle
2007-10-11 13:35 ` Maciej W. Rozycki
2007-10-11 14:00 ` Ralf Baechle
2007-10-11 14:49 ` Maciej W. Rozycki
2007-10-14 19:42 ` Franck Bui-Huu [this message]
2007-10-15 16:01 ` Ralf Baechle
2007-10-16 8:33 ` Franck Bui-Huu
2007-10-11 13:19 ` Maciej W. Rozycki
2007-10-14 19:52 ` Franck Bui-Huu
2007-10-15 12:19 ` Maciej W. Rozycki
2007-10-15 20:06 ` Franck Bui-Huu
2007-10-16 10:29 ` Maciej W. Rozycki
2007-10-18 20:28 ` Franck Bui-Huu
2007-10-19 11:59 ` Maciej W. Rozycki
2007-11-04 8:29 ` Franck Bui-Huu
2007-11-05 12:38 ` Maciej W. Rozycki
2007-11-05 20:32 ` Franck Bui-Huu
2007-10-11 15:26 ` Thiemo Seufer
2007-10-11 16:16 ` Maciej W. Rozycki
2007-10-11 16:25 ` Ralf Baechle
2007-10-11 17:07 ` Maciej W. Rozycki
2007-10-11 16:39 ` Thiemo Seufer
2007-10-14 19:53 ` Franck Bui-Huu
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=47127110.4060206@gmail.com \
--to=vagabon.xyz@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.