Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@redhat.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: Richard Henderson <rth@redhat.com>,
	John David Anglin <dave@hiauly1.hia.nrc.ca>,
	gcc-patches@gcc.gnu.org, parisc-linux@puffin.external.hp.com
Subject: Re: Oust HPPA PIC_OFFSET_TABLE_REGNUM_SAVED
Date: Tue, 16 Jan 2001 22:30:36 -0700	[thread overview]
Message-ID: <22207.979709436@upchuck.cygnus.com> (raw)
In-Reply-To: Your message of Tue, 16 Jan 2001 20:28:12 +1100. <Pine.LNX.4.21.0101161848180.4272-100000@front.linuxcare.com.au>

 In message <Pine.LNX.4.21.0101161848180.4272-100000@front.linuxcare.com.au>yo
u write:
  > +  if (flag_pic
  > +      && (GET_CODE (PIC_OFFSET_TABLE_SAVE_RTX) != REG
  > +	  || HARD_REGISTER_P (PIC_OFFSET_TABLE_SAVE_RTX)))
  > +    emit_move_insn (PIC_OFFSET_TABLE_SAVE_RTX,
  >  		    gen_rtx_REG (word_mode, PIC_OFFSET_TABLE_REGNUM));
I do have a question about this particular hunk of code.

I can't think of a condition where PIC_OFFSET_TABLE_SAVE_RTX would not be
a reg when this code was executed.  Simlarly I can't think of a case where
it would be a hard reg.

I think we should just emit the insn unconditionally unless you're aware
of some reason we can't shouldn't.

We're probably also going to need to emit a use of the %r19 and maybe %r27
on the return insns to ensure the pic register is restored after the
final call in any given function.

jeff

  parent reply	other threads:[~2001-01-17  5:24 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 [this message]
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
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=22207.979709436@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