From: Gabriel Paubert <paubert@iram.es>
To: David Miller <davem@davemloft.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] Fix bootwrapper builds with newer gcc versions
Date: Mon, 5 May 2008 13:55:37 +0200 [thread overview]
Message-ID: <20080505115537.GA16128@iram.es> (raw)
In-Reply-To: <20080503.005510.88048425.davem@davemloft.net>
On Sat, May 03, 2008 at 12:55:10AM -0700, David Miller wrote:
> From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Date: Sat, 03 May 2008 17:50:17 +1000
>
> > Best would be if we could get those runtime bits linked in the module
> > itself, but I don't know enough about our toolchain to know if that's
> > easy (I suppose everything is always possible :-)
>
> The only downside is that you'd have N copies of these
> routines, one for every module that emmited the libcalls.
It's probably not as bad as it seems:
1) it will be smaller than having the saved/restore inlined in every
function prologue and epilogue
2) as soon as you have ten functions or so that call them, it might
even be smaller than the size of all the trampolines. Unless I'm
mistaken, you would need at least two trampolines for every entry
point that you use in the save/restore routines, which have an entry
point at every instruction boundary or so. That's about 32 bytes
(8 instructions) per set of save/restore functions IIRC.
The ultimate solution might be lo link all these routines at a fixed
large absolute address (between -32M and -1UL) so that you can
call them with a bla instruction. But this requires memory layout
changes which would be quite painful.
Regards,
Gabriel
next prev parent reply other threads:[~2008-05-05 11:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 8:11 [PATCH] [POWERPC] Fix bootwrapper builds with newer gcc versions Kumar Gala
2008-05-02 11:54 ` Segher Boessenkool
2008-05-02 13:28 ` Kumar Gala
2008-05-02 13:37 ` Segher Boessenkool
2008-05-02 13:41 ` Kumar Gala
2008-05-02 15:20 ` Scott Wood
2008-05-02 17:15 ` Segher Boessenkool
2008-05-02 14:09 ` Kumar Gala
2008-05-02 17:11 ` Segher Boessenkool
2008-05-02 21:28 ` Kumar Gala
2008-05-02 21:40 ` David Miller
2008-05-02 21:58 ` Kumar Gala
2008-05-02 23:27 ` Benjamin Herrenschmidt
2008-05-02 23:38 ` David Miller
2008-05-03 0:06 ` Segher Boessenkool
2008-05-03 7:50 ` Benjamin Herrenschmidt
2008-05-03 7:55 ` David Miller
2008-05-03 11:01 ` Benjamin Herrenschmidt
2008-05-05 11:55 ` Gabriel Paubert [this message]
2008-05-02 12:13 ` Josh Boyer
2008-05-02 13:32 ` Kumar Gala
2008-05-02 13:53 ` Josh Boyer
2008-05-02 13:59 ` Kumar Gala
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=20080505115537.GA16128@iram.es \
--to=paubert@iram.es \
--cc=davem@davemloft.net \
--cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).