Linux PARISC architecture development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: deller@gmx.de, linux-parisc@vger.kernel.org
Subject: Re: [RFC] fix the relative jump problem on large modules
Date: Sun, 20 Jun 2010 08:55:28 -0500	[thread overview]
Message-ID: <1277042128.5242.2.camel@mulgrave.site> (raw)
In-Reply-To: <20100619232128.6010C5160@hiauly1.hia.nrc.ca>

On Sat, 2010-06-19 at 19:21 -0400, John David Anglin wrote:
> > The theory was that the linker should do the right thing and not emit a
> > relocation that can't reach the boundary of the text segment (i.e. it
> > should embed a stub between the sections as it combines them).  I'll
> > have to fire up a 32 bit compile and see exactly what it thinks it's
> > doing ... I've got a nasty feeling it expects us to be able to stub
> > either at the beginning or the end, which the in-kernel loader doesn't.
> 
> See ld --stub-group-size=N option.

I was assuming that was the default, like on arm, I take it it's not?

>   GCC assumes stub sections are at
> the beginning and that the linker can insert stubs between input sections.
> Merging text sections is likely to cause problems.

Well, the theory was that ld was capable of more intelligent section
layout decisions than the in-kernel linker.  If you're saying that's not
true, then there's probably not much point to doing this.

James



  reply	other threads:[~2010-06-20 13:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-18 15:03 [RFC] fix the relative jump problem on large modules James Bottomley
2010-06-18 20:40 ` Helge Deller
2010-06-19 22:21   ` Helge Deller
2010-06-19 22:57     ` James Bottomley
2010-06-19 23:21       ` John David Anglin
2010-06-20 13:55         ` James Bottomley [this message]
2010-06-20 14:35           ` John David Anglin

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=1277042128.5242.2.camel@mulgrave.site \
    --to=james.bottomley@hansenpartnership.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=deller@gmx.de \
    --cc=linux-parisc@vger.kernel.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