From: Jeffrey A Law <law@cygnus.com>
To: Alan Modra <alan@linuxcare.com.au>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Get rid of %r8 linker stubs
Date: Thu, 22 Jun 2000 14:35:39 -0600 [thread overview]
Message-ID: <16486.961706139@upchuck> (raw)
In-Reply-To: Your message of Thu, 22 Jun 2000 14:33:09 MDT. <E135Dev-0007ho-00@noam.fc.hp.com>
> = Hello all,
> = The attached patch to puffin.external.hp.com CVS binutils-2.10
> = implements a new linker stub scheme for elf32-hppa. (Well, it's new for
> = gnu - I believe the hp linker does something like this).
> =
> = The new scheme works like this: For any linker input section that needs
> a
> = stub to reach called routines, the linker creates a stub section located
> = immediately prior to the input section. A call is simply redirected to
> = the stub, which consists of a long branch
> = ldil LR'XXX,%r1
> = be,n RR'XXX(%sr4,%r1)
> = to the destination.
An FYI -- this is precisely the kind of scheme that I've wanted to see
for the GNU PA tools.
I'd like to get this code integrated into the official binutils releases.
> = to the implicit %r31 used by "be,l". Additionally, when we finally
> = implement elf32-hppa shared libraries, there are going to be a _lot_ more
> = stubs. We may even exceed the maximum 256k of stubs, especially if we tr
> = to combine .plt and .got with stubs to get a register back.
Not only that, the old scheme was not relocatable since it assumed all the
stubs sat in the first 256k of the address space .
jeff
next prev parent reply other threads:[~2000-06-22 20:46 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 [this message]
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
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=16486.961706139@upchuck \
--to=law@cygnus.com \
--cc=alan@linuxcare.com.au \
--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