From: Andreas Schwab <schwab@suse.de>
To: Richard Henderson <rth@redhat.com>
Cc: Peter Barada <pbarada@mail.wm.sps.mot.com>,
Peter.Barada@motorola.com, gcc@gcc.gnu.org
Subject: Re: Saga of m68k PIC continues
Date: Thu, 12 Dec 2002 11:28:00 -0000 [thread overview]
Message-ID: <jebs3r9klg.fsf@sykes.suse.de> (raw)
In-Reply-To: <20021212180017.GB7861@redhat.com> (Richard Henderson's message of "Thu, 12 Dec 2002 10:00:17 -0800")
Richard Henderson <rth@redhat.com> writes:
|> On Thu, Dec 12, 2002 at 11:41:23AM +0100, Andreas Schwab wrote:
|> > For -fPIC there is probably no difference, but full 32-bit pc-relative is
|> > still less efficient than register+16 bit offset, so with -fpic the use of
|> > the pic register is usually faster.
|>
|> Even though you've got to have an extra memory load? I mean, for
|> a *static* variable, your choices for computing the address are
For a static variable you are right. I was thinking about non-static
variables, i.e @GOT vs @GOTPC.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2002-12-12 18:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 12:57 Peter Barada
2002-12-11 14:25 ` Jim Wilson
2002-12-11 16:11 ` Richard Henderson
2002-12-11 16:19 ` Peter Barada
2002-12-12 2:41 ` Richard Henderson
2002-12-12 5:11 ` Andreas Schwab
2002-12-12 11:24 ` Richard Henderson
2002-12-12 11:28 ` Andreas Schwab [this message]
2002-12-12 12:27 ` Peter Barada
2002-12-12 12:44 ` Jan Hubicka
2002-12-12 12:44 ` Peter Barada
2002-12-12 13:00 ` Jan Hubicka
2002-12-12 13:46 ` Peter Barada
2002-12-12 14:32 ` Jim Wilson
2002-12-12 13:50 ` Peter Barada
2002-12-12 13:59 ` Jan Hubicka
2002-12-12 14:57 ` Richard Henderson
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=jebs3r9klg.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=Peter.Barada@motorola.com \
--cc=gcc@gcc.gnu.org \
--cc=pbarada@mail.wm.sps.mot.com \
--cc=rth@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).