From: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] Fix PR / 17317
Date: Mon, 11 Oct 2004 06:06:00 -0000 [thread overview]
Message-ID: <416A15EA.5050605@codito.com> (raw)
Hi,
The patch inlined below fixes PR/ 17317 . The earlier definitions of
REG_OK_FOR_BASE, REGNO_OK_FOR_BASE , REG_OK_FOR_INDEX, REGNO_OK_INDEX
did not consider blink ( r31) as a valid base address. The documentation
for the A4 does not contradict this.
The patch below is for the 3.4 branch and can also be applied to cvs head.
cheers
Ramana
ChangeLog:
2004-10-11: Ramana Radhakrishnan (ramana.radhakrishnan@codito.com)
arc.h :
Fix PR/17317. Allow for blink to be used as a base register.
Index: arc.h
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/arc/arc.h,v
retrieving revision 1.68.4.1
diff -a -u -r1.68.4.1 arc.h
--- arc.h 9 Mar 2004 02:59:54 -0000 1.68.4.1
+++ arc.h 11 Oct 2004 04:51:32 -0000
@@ -463,9 +463,9 @@
Since they use reg_renumber, they are safe only once reg_renumber
has been allocated, which happens in local-alloc.c. */
#define REGNO_OK_FOR_BASE_P(REGNO) \
-((REGNO) < 29 || (unsigned) reg_renumber[REGNO] < 29)
+((REGNO) < 32 || (unsigned) reg_renumber[REGNO] < 32)
#define REGNO_OK_FOR_INDEX_P(REGNO) \
-((REGNO) < 29 || (unsigned) reg_renumber[REGNO] < 29)
+((REGNO) < 32 || (unsigned) reg_renumber[REGNO] < 32)
/* Given an rtx X being reloaded into a reg required to be
in class CLASS, return the class of reg to actually use.
@@ -900,11 +900,11 @@
/* Nonzero if X is a hard reg that can be used as an index
or if it is a pseudo reg. */
#define REG_OK_FOR_INDEX_P(X) \
-((unsigned) REGNO (X) - 29 >= FIRST_PSEUDO_REGISTER - 29)
+((unsigned) REGNO (X) - 32 >= FIRST_PSEUDO_REGISTER - 32)
/* Nonzero if X is a hard reg that can be used as a base reg
or if it is a pseudo reg. */
#define REG_OK_FOR_BASE_P(X) \
-((unsigned) REGNO (X) - 29 >= FIRST_PSEUDO_REGISTER - 29)
+((unsigned) REGNO (X) - 32 >= FIRST_PSEUDO_REGISTER - 32)
#else
reply other threads:[~2004-10-11 5:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=416A15EA.5050605@codito.com \
--to=ramana.radhakrishnan@codito.com \
--cc=gcc-patches@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).