From: Richard Sandiford <richard.sandiford@arm.com>
To: jlaw@ventanamicro.com, vmakarov@redhat.com, gcc-patches@gcc.gnu.org
Cc: Richard Sandiford <richard.sandiford@arm.com>
Subject: [PATCH 5/5] Add an aligned_register_operand predicate
Date: Sun, 12 Nov 2023 14:52:29 +0000 [thread overview]
Message-ID: <20231112145229.2924713-6-richard.sandiford@arm.com> (raw)
In-Reply-To: <20231112145229.2924713-1-richard.sandiford@arm.com>
This patch adds a target-independent aligned_register_operand
predicate, for use with register constraints that use filters
to impose an alignment. The definition deliberately jetisons
some of the historical baggage in general_operand.
gcc/
* common.md (aligned_register_operand): New predicate.
---
gcc/common.md | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/gcc/common.md b/gcc/common.md
index 51ecd79786b..91a72bd7731 100644
--- a/gcc/common.md
+++ b/gcc/common.md
@@ -17,6 +17,34 @@
;; along with GCC; see the file COPYING3. If not see
;; <http://www.gnu.org/licenses/>. */
+;; This predicate is intended to be paired with register constraints that use
+;; register filters to impose an alignment. Operands that are aligned via
+;; TARGET_HARD_REGNO_MODE_OK should use normal register_operands instead.
+(define_predicate "aligned_register_operand"
+ (match_code "reg,subreg")
+{
+ /* Require the offset in a non-paradoxical subreg to be naturally aligned.
+ For example, if we have a subreg of something that is double the size of
+ this operand, the offset must select the first or second half of it. */
+ if (SUBREG_P (op)
+ && multiple_p (SUBREG_BYTE (op), GET_MODE_SIZE (GET_MODE (op))))
+ op = SUBREG_REG (op);
+ if (!REG_P (op))
+ return false;
+
+ if (HARD_REGISTER_P (op))
+ {
+ if (!in_hard_reg_set_p (operand_reg_set, GET_MODE (op), REGNO (op)))
+ return false;
+
+ /* Reject hard registers that would need reloading, so that the reload
+ is visible to IRA and to pre-RA optimizers. */
+ if (REGNO (op) % REG_NREGS (op) != 0)
+ return false;
+ }
+ return true;
+})
+
(define_register_constraint "r" "GENERAL_REGS"
"Matches any general register.")
--
2.25.1
next prev parent reply other threads:[~2023-11-12 14:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 14:52 [PATCH 0/5] Add support for operand-specific alignment requirements Richard Sandiford
2023-11-12 14:52 ` [PATCH 1/5] Add register filter operand to define_register_constraint Richard Sandiford
2023-11-19 21:49 ` Jeff Law
2023-11-12 14:52 ` [PATCH 2/5] recog: Handle register filters Richard Sandiford
2023-11-19 21:51 ` Jeff Law
2023-11-12 14:52 ` [PATCH 3/5] lra: " Richard Sandiford
2023-11-12 14:52 ` [PATCH 4/5] ira: " Richard Sandiford
2023-11-12 14:52 ` Richard Sandiford [this message]
2023-11-19 21:52 ` [PATCH 5/5] Add an aligned_register_operand predicate Jeff Law
2023-11-14 0:01 ` [PATCH 0/5] Add support for operand-specific alignment requirements Vladimir Makarov
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=20231112145229.2924713-6-richard.sandiford@arm.com \
--to=richard.sandiford@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jlaw@ventanamicro.com \
--cc=vmakarov@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).