From: willy@thepuffingroup.com
To: Alan Modra <alan@linuxcare.com.au>
Cc: Paul Bame <bame@fc.hp.com>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Get rid of %r8 linker stubs
Date: Tue, 4 Jul 2000 10:21:54 -0400 [thread overview]
Message-ID: <20000704102154.Q12436@vodka.thepuffingroup.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0006231116510.24137-100000@front.linuxcare.com.au>; from Alan Modra on Fri, Jun 23, 2000 at 11:45:16AM +1000
On Fri, Jun 23, 2000 at 11:45:16AM +1000, Alan Modra wrote:
> No, gcc doesn't need to be rebuilt. The problem here (I think - I'm going
> to build a kernel in a the moment) is the silly use of "ld -r" in the
> kernel build process. This has the unfortunate effect of concatenating
> all the .text sections, making some too large for a branch to reach its
> stub section. Of course this same thing can happen with very large object
> files.
>
> One fairly simple work-around is to use -ffunction-sections when compiling,
> as then you need a truely enormous function (> 4*2**(17-1) bytes long)
> before you'll get "cannot reach stub" Also, gcc has support for handling
> even these enormous functions.
how about
--split-by-reloc COUNT Split output sections every COUNT relocs
would that help?
--
The Sex Pistols were revolutionaries. The Bay City Rollers weren't.
next prev parent reply other threads:[~2000-07-04 15:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-21 14:07 [parisc-linux] Get rid of %r8 linker stubs Alan Modra
2000-06-22 20:33 ` Paul Bame
2000-06-22 20:35 ` Jeffrey A Law
2000-06-23 1:45 ` Alan Modra
2000-06-23 10:34 ` Alan Modra
2000-07-03 19:15 ` willy
2000-07-04 14:21 ` willy [this message]
2000-07-05 0:38 ` Alan Modra
-- strict thread matches above, loose matches on Subject: below --
2000-07-04 22:33 bame
2000-07-05 0:36 ` Alan Modra
2000-07-05 0:57 ` Ulrich Drepper
2000-07-05 1:52 ` bame
2000-07-05 2:38 ` Alan Modra
2000-07-05 1:55 ` Alan Modra
2000-07-05 2:58 ` bame
2000-07-05 6:43 ` Patric Karlstrom
2000-07-05 6:26 ` willy
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=20000704102154.Q12436@vodka.thepuffingroup.com \
--to=willy@thepuffingroup.com \
--cc=alan@linuxcare.com.au \
--cc=bame@fc.hp.com \
--cc=parisc-linux@thepuffingroup.com \
/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