public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-6638] xtensa: Remove REG_OK_STRICT and its derivatives
Date: Mon, 13 Mar 2023 17:06:17 +0000 (GMT)	[thread overview]
Message-ID: <20230313170617.12FCD3858D39@sourceware.org> (raw)

https://gcc.gnu.org/g:c981f61c071757f1f724fe7c3959622c13f079fa

commit r13-6638-gc981f61c071757f1f724fe7c3959622c13f079fa
Author: Takayuki 'January June' Suwa <jjsuwa_sys3175@yahoo.co.jp>
Date:   Mon Mar 13 09:37:10 2023 +0900

    xtensa: Remove REG_OK_STRICT and its derivatives
    
    Because GO_IF_LEGITIMATE_ADDRESS was deprecated a long time ago
    (see commit c6c3dba931548987c78719180e30ebc863404b89).
    
    gcc/ChangeLog:
    
            * config/xtensa/xtensa.h (REG_OK_STRICT, REG_OK_FOR_INDEX_P,
            REG_OK_FOR_BASE_P): Remove.

Diff:
---
 gcc/config/xtensa/xtensa.h | 11 +----------
 1 file changed, 1 insertion(+), 10 deletions(-)

diff --git a/gcc/config/xtensa/xtensa.h b/gcc/config/xtensa/xtensa.h
index 058602e44ee..8ebf37cab33 100644
--- a/gcc/config/xtensa/xtensa.h
+++ b/gcc/config/xtensa/xtensa.h
@@ -590,19 +590,10 @@ typedef struct xtensa_args
 /* C expressions that are nonzero if X (assumed to be a `reg' RTX) is
    valid for use as a base or index register.  */
 
-#ifdef REG_OK_STRICT
-#define REG_OK_STRICT_FLAG 1
-#else
-#define REG_OK_STRICT_FLAG 0
-#endif
-
 #define BASE_REG_P(X, STRICT)						\
-  ((!(STRICT) && REGNO (X) >= FIRST_PSEUDO_REGISTER)			\
+  ((!(STRICT) && ! HARD_REGISTER_P (X))					\
    || REGNO_OK_FOR_BASE_P (REGNO (X)))
 
-#define REG_OK_FOR_INDEX_P(X) 0
-#define REG_OK_FOR_BASE_P(X) BASE_REG_P (X, REG_OK_STRICT_FLAG)
-
 /* Maximum number of registers that can appear in a valid memory address.  */
 #define MAX_REGS_PER_ADDRESS 1

                 reply	other threads:[~2023-03-13 17:06 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=20230313170617.12FCD3858D39@sourceware.org \
    --to=jcmvbkbc@gcc.gnu.org \
    --cc=gcc-cvs@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).