From: Alan Modra <amodra@gmail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
Paul Mackerras <paulus@samba•org>,
linuxppc-dev@lists•ozlabs.org
Subject: Re: linux-next: build failure after merge of the final tree
Date: Fri, 6 Jul 2012 15:38:34 +0930 [thread overview]
Message-ID: <20120706060834.GC5805@bubble.grove.modra.org> (raw)
In-Reply-To: <20120706130137.6aae96c0072af1f330249c0d@canb.auug.org.au>
On Fri, Jul 06, 2012 at 01:01:37PM +1000, Stephen Rothwell wrote:
> solos-pci.c:(.text+0x1ff923c): relocation truncated to fit: R_PPC64_REL24
^^^^^^^^^
> I assume at this point, we are just too large.
Yeah, but not in total. I didn't see any of these in the allyes
kernel I built with our proof of concept hack to avoid ld -r. I think
you'll find that these are all from ld -r output, as I assume no one
in kernel land writes drivers or whatever with 33M of text in a single
file. Branches in that monstrous section can't even reach the
trampolines that ld inserts to extend branch reach. Did I mention
that ld -r is a bad idea?
One workaround might be to compile with -ffunction-sections.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2012-07-06 6:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 8:33 linux-next: build failure after merge of the final tree Stephen Rothwell
2012-07-05 9:43 ` Alan Modra
2012-07-06 0:21 ` Stephen Rothwell
2012-07-06 0:57 ` Alan Modra
2012-07-06 3:01 ` Stephen Rothwell
2012-07-06 6:08 ` Alan Modra [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-06 9:28 Stephen Rothwell
2014-01-06 23:12 ` Benjamin Herrenschmidt
2013-08-20 7:20 Stephen Rothwell
2013-08-20 16:07 ` Dwight Engen
2013-08-20 19:28 ` Ben Myers
2013-08-21 0:22 ` Stephen Rothwell
2013-08-21 15:54 ` Ben Myers
2013-08-20 20:46 ` Arnd Bergmann
2013-08-21 5:08 ` Dwight Engen
2013-08-21 6:30 ` Jeremy Kerr
2013-08-21 15:56 ` Ben Myers
2012-02-27 6:37 Stephen Rothwell
2012-02-27 9:19 ` Benjamin Herrenschmidt
2012-02-27 23:30 ` Benjamin Herrenschmidt
2012-01-20 7:21 Stephen Rothwell
2012-01-20 9:08 ` Deepthi Dharwar
2011-07-18 9:35 Stephen Rothwell
2011-01-31 6:26 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=20120706060834.GC5805@bubble.grove.modra.org \
--to=amodra@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=paulus@samba$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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