From: Alan Modra <amodra@bigpond.net.au>
To: Andreas Schwab <schwab@suse.de>
Cc: binutils@sources.redhat.com
Subject: Re: powerpc new PLT and GOT
Date: Wed, 11 May 2005 15:39:00 -0000 [thread overview]
Message-ID: <20050511151614.GD29302@bubble.grove.modra.org> (raw)
In-Reply-To: <je64xpn701.fsf@sykes.suse.de>
On Wed, May 11, 2005 at 04:59:26PM +0200, Andreas Schwab wrote:
> Alan Modra <amodra@bigpond.net.au> writes:
>
> > Then, given that .glink doesn't really fit the traditional .plt, I don't
> > want to use .got.plt because I feel some section ought to be called
> > .plt, simply because that's the traditional name for sections associated
> > with dynamic function linkage. Powerpc64 also has a .plt that just
> > consists of data.
>
> How about .got.glink then? Calling a section that has GOT nature .plt can
> be confusing.
I want to call _something_ .plt, that's my main reason for not using
.got.plt. It's not that I dislike the name .got.plt.
The other reason for choosing .glink and .plt is that these are the
sections used by PowerPC64 Linux, with ppc64 .glink being a code section
and ppc64 .plt a (BSS) data section.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2005-05-11 15:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 14:22 Alan Modra
2005-05-11 14:29 ` Daniel Jacobowitz
2005-05-11 14:59 ` Alan Modra
2005-05-11 15:10 ` Andreas Schwab
2005-05-11 15:39 ` Alan Modra [this message]
2005-05-11 15:16 ` Daniel Jacobowitz
2005-05-11 16:37 ` Richard Earnshaw
2005-05-11 14:45 ` Andreas Schwab
2005-05-12 6:08 ` Richard Henderson
2005-05-12 6:13 ` Alan Modra
2005-05-12 7:47 ` Richard Henderson
2005-05-12 9:02 ` Alan Modra
2005-05-12 16:10 ` Alan Modra
2005-05-12 18:07 ` Richard Henderson
2005-05-14 5:57 ` Alan Modra
2005-05-17 14:16 ` Alan Modra
2005-05-19 8:32 ` Alan Modra
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=20050511151614.GD29302@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=schwab@suse.de \
/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).