From: Stan Shebs <shebs@apple.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: dalej@apple.com, gcc@gcc.gnu.org
Subject: Re: dynamic PIC register?
Date: Thu, 27 Sep 2001 06:38:00 -0000 [thread overview]
Message-ID: <3BB32B8F.EBEC6ABF@apple.com> (raw)
In-Reply-To: <orbsjxypjx.fsf@localhost.localdomain>
Alexandre Oliva wrote:
>
> On Sep 20, 2001, dalej@apple.com wrote:
>
> > On the Darwin powerpc target, it would be better not to have
> > PIC_OFFSET_TABLE_REGNUM be a fixed register.
>
> I don't know anything about the implementation of shared libraries on
> ppc, but if it uses a procedure linkage table, I don't see how the PIC
> register may vary: the PLT in general depends on a specific register
> pointing to the GOT (plus or minus some constant).
No PLT or GOT. The PIC register is set up per-function. The Darwin
PIC strategy is unlike any other, one reason why there is a lot of code
in config/darwin.*.
Stan
prev parent reply other threads:[~2001-09-27 6:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 17:20 dalej
2001-09-20 18:55 ` David Edelsohn
2001-09-24 13:04 ` Geoff Keating
2001-09-27 5:40 ` Alexandre Oliva
2001-09-27 6:27 ` Andreas Schwab
2001-09-27 6:38 ` Stan Shebs [this message]
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=3BB32B8F.EBEC6ABF@apple.com \
--to=shebs@apple.com \
--cc=aoliva@redhat.com \
--cc=dalej@apple.com \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).