From: Michael Ellerman <michael@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: ppc-dev <linuxppc-dev@lists.ozlabs.org>, Alan Modra <amodra@gmail.com>
Subject: Re: [PATCH] powerpc: put the gpr sabe/restore functions in their own section
Date: Sat, 07 Jul 2012 16:55:21 +1000 [thread overview]
Message-ID: <1341644121.30371.2.camel@concordia> (raw)
In-Reply-To: <20120706170940.e3457b04a58ddd18d963c14a@canb.auug.org.au>
On Fri, 2012-07-06 at 17:09 +1000, Stephen Rothwell wrote:
> This allows the linker to know that calls to them do not need to switch
> TOC and stop errors like the following when linking large configurations:
> arch/powerpc/lib/crtsavres.S | 5 ++++-
You didn't make any change to the linker script? How does this section
get in there? I don't see a .text* anywhere?
> diff --git a/arch/powerpc/lib/crtsavres.S b/arch/powerpc/lib/crtsavres.S
> index 1c893f0..b2c68ce 100644
> --- a/arch/powerpc/lib/crtsavres.S
> +++ b/arch/powerpc/lib/crtsavres.S
> @@ -41,12 +41,13 @@
> #include <asm/ppc_asm.h>
>
> .file "crtsavres.S"
> - .section ".text"
>
> #ifdef CONFIG_CC_OPTIMIZE_FOR_SIZE
>
> #ifndef CONFIG_PPC64
>
> + .section ".text"
> +
> /* Routines for saving integer registers, called by the compiler. */
> /* Called with r11 pointing to the stack header word of the caller of the */
> /* function, just beyond the end of the integer save area. */
> @@ -232,6 +233,8 @@ _GLOBAL(_rest32gpr_31_x)
>
> #else /* CONFIG_PPC64 */
>
> + .section ".text.save.restore","ax",@progbits
> +
> .globl _savegpr0_14
> _savegpr0_14:
> std r14,-144(r1)
Any reason to not put the 32-bit versions in the same section? AFAICS
nothing in that file uses the TOC.
cheers
next prev parent reply other threads:[~2012-07-07 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 7:09 [PATCH] powerpc: put the gpr sabe/restore functions in their own section Stephen Rothwell
2012-07-07 6:55 ` Michael Ellerman [this message]
2012-07-08 23:50 ` Stephen Rothwell
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=1341644121.30371.2.camel@concordia \
--to=michael@ellerman.id.au \
--cc=amodra@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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).