From: Jeffrey A Law <law@redhat.com>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: alan@linuxcare.com.au, rth@redhat.com, gcc-patches@gcc.gnu.org,
parisc-linux@puffin.external.hp.com
Subject: Re: Oust HPPA PIC_OFFSET_TABLE_REGNUM_SAVED
Date: Wed, 17 Jan 2001 14:42:12 -0700 [thread overview]
Message-ID: <25409.979767732@upchuck.cygnus.com> (raw)
In-Reply-To: Your message of Wed, 17 Jan 2001 11:22:36 EST. <200101171622.LAA13215@hiauly1.hia.nrc.ca>
In message <200101171622.LAA13215@hiauly1.hia.nrc.ca>you write:
> I think all these problems can be resolved by emitting the insn at the
> first call. We just have to keep track of whether it has been emitted
> or not.
I'm not entirely sure what you mean by this.
We must emit the code to restore the PIC register after each call when
generating PIC code. There are no known exceptions to this rule.
You might be talking about saving the PIC register into the stack or
pseudo during the prologue. Yes, we could arrange to do that if and
only if we had a call in PIC mode. That's fairly easy to do.
jeff
next prev parent reply other threads:[~2001-01-17 22:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0101151238510.21322-100000@front.linuxcare.com.au>
2001-01-15 11:09 ` [parisc-linux] Oust HPPA PIC_OFFSET_TABLE_REGNUM_SAVED Alan Modra
2001-01-15 16:24 ` John David Anglin
2001-01-15 16:38 ` Jeffrey A Law
2001-01-15 23:17 ` Alan Modra
2001-01-15 17:46 ` Jeffrey A Law
2001-01-15 23:07 ` Alan Modra
2001-01-16 1:20 ` Alan Modra
2001-01-16 5:53 ` Richard Henderson
2001-01-16 9:28 ` Alan Modra
2001-01-17 3:23 ` John David Anglin
2001-01-17 3:54 ` John David Anglin
2001-01-17 5:26 ` Jeffrey A Law
2001-01-17 5:30 ` Jeffrey A Law
2001-01-17 5:59 ` John David Anglin
2001-01-17 7:24 ` Alan Modra
2001-01-17 16:09 ` Jeffrey A Law
2001-01-17 16:22 ` John David Anglin
2001-01-17 21:42 ` Jeffrey A Law [this message]
2001-01-17 22:20 ` John David Anglin
2001-01-18 6:04 ` John David Anglin
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=25409.979767732@upchuck.cygnus.com \
--to=law@redhat.com \
--cc=alan@linuxcare.com.au \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gcc-patches@gcc.gnu.org \
--cc=parisc-linux@puffin.external.hp.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