public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rearnsha@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, iant@palmchip.com,
	pb@gcc.gnu.org, rearnsha@gcc.gnu.org
Subject: Re: target/592: [ARM/Thumb] Poor choice of PIC register
Date: Tue, 23 Apr 2002 08:44:00 -0000	[thread overview]
Message-ID: <20020423154421.24994.qmail@sources.redhat.com> (raw)

Synopsis: [ARM/Thumb] Poor choice of PIC register

Responsible-Changed-From-To: pb->rearnsha
Responsible-Changed-By: rearnsha
Responsible-Changed-When: Tue Apr 23 08:44:20 2002
Responsible-Changed-Why:
    .
State-Changed-From-To: analyzed->suspended
State-Changed-By: rearnsha
State-Changed-When: Tue Apr 23 08:44:20 2002
State-Changed-Why:
    Having given this some consideration, I'm no-longer convinced that
    fixing a lo reigster is a good idea: it would unduly pessimize
    other code and might lead to situations where we would run
    out of registers.
    The best solution would be to make the PIC register a pseudo,
    but apparently there are other issues that prevent this.
    
    I believe the orignal problem that provoked this report has now
    been resolved.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=592


             reply	other threads:[~2002-04-23 15:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23  8:44 rearnsha [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-22  3:05 pb

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=20020423154421.24994.qmail@sources.redhat.com \
    --to=rearnsha@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=iant@palmchip.com \
    --cc=pb@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).