From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Bottomley Subject: Re: [RFC] fix the relative jump problem on large modules Date: Sun, 20 Jun 2010 08:55:28 -0500 Message-ID: <1277042128.5242.2.camel@mulgrave.site> References: <20100619232128.6010C5160@hiauly1.hia.nrc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Cc: deller@gmx.de, linux-parisc@vger.kernel.org To: John David Anglin Return-path: In-Reply-To: <20100619232128.6010C5160@hiauly1.hia.nrc.ca> List-ID: List-Id: linux-parisc.vger.kernel.org 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