From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Matt Fleming <matt@console-pimps.org>
Cc: linux-arch@vger.kernel.org, Kyle McMartin <kyle@mcmartin.ca>,
linux-kernel@vger.kernel.org,
Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH 4/5] parisc: Remove *(.text.*) pattern from the linker script
Date: Mon, 14 Jun 2010 10:20:59 -0500 [thread overview]
Message-ID: <1276528859.5374.29.camel@mulgrave.site> (raw)
In-Reply-To: <1276519112-11649-4-git-send-email-matt@console-pimps.org>
On Mon, 2010-06-14 at 13:38 +0100, Matt Fleming wrote:
> From: Matt Fleming <matthew.fleming@imgtec.com>
>
> Drop the pattern from the linker script because the pattern is now
> provided by TEXT_TEXT.
>
> Signed-off-by: Matt Fleming <matthew.fleming@imgtec.com>
> ---
> arch/parisc/kernel/vmlinux.lds.S | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/arch/parisc/kernel/vmlinux.lds.S b/arch/parisc/kernel/vmlinux.lds.S
> index d64a6bb..6784e39 100644
> --- a/arch/parisc/kernel/vmlinux.lds.S
> +++ b/arch/parisc/kernel/vmlinux.lds.S
> @@ -61,7 +61,6 @@ SECTIONS
> *(.text.sys_exit)
> *(.text.do_sigaltstack)
> *(.text.do_fork)
> - *(.text.*)
> *(.fixup)
> *(.lock.text) /* out-of-line lock text */
> *(.gnu.warning)
This would destroy all of the named parisc text ordering we do above the
removed line because now you'd have swept up all the function sections
before we get to them, won't it?
The ordering is an execution speed up on 32 bit systems because our
relative jump is so short.
James
next parent reply other threads:[~2010-06-14 15:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1276519112-11649-1-git-send-email-matt@console-pimps.org>
[not found] ` <1276519112-11649-4-git-send-email-matt@console-pimps.org>
2010-06-14 15:20 ` James Bottomley [this message]
2010-06-14 19:13 ` [PATCH 4/5] parisc: Remove *(.text.*) pattern from the linker script Matt Fleming
[not found] ` <alpine.DEB.1.10.1006141014360.1432@dr-wily.mit.edu>
[not found] ` <87y6ehxvby.fsf@linux-g6p1.site>
[not found] ` <1276545951.5374.260.camel@mulgrave.site>
[not found] ` <alpine.DEB.1.10.1006141608550.1248@dr-wily.mit.edu>
2010-06-14 23:08 ` [PATCH 1/5] vmlinux.lds.h: Include *(.text.*) in TEXT_TEXT James Bottomley
2010-06-15 2:45 ` Tim Abbott
2010-06-16 21:40 ` James Bottomley
2010-06-17 19:11 ` Denys Vlasenko
2010-06-17 19:56 ` James Bottomley
2010-06-17 20:19 ` Denys Vlasenko
2010-06-17 20:38 ` James Bottomley
[not found] ` <alpine.DEB.1.10.1006141534490.1248@dr-wily.mit.edu>
2010-06-14 23:14 ` James Bottomley
2010-06-15 2:52 ` Tim Abbott
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=1276528859.5374.29.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=kyle@mcmartin.ca \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=matt@console-pimps.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