From: Hans-Peter Nilsson <hp@axis.com>
Date: Tue, 28 Mar 2023 01:23:33 +0000 (+0200)
Subject: CRIS: Correct "T" to define_memory_constraint, not define_constraint
X-Git-Tag: basepoints/gcc-14~322
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c4d61d3186b5f3db1f4823127ab11b5ff465a872;p=thirdparty%2Fgcc.git

CRIS: Correct "T" to define_memory_constraint, not define_constraint

This patch has no effect on builds using reload of libgcc, newlib libc, my
own at-a-glance-testsuite and coremark.  That somewhat surprisingly
also goes for LRA builds, even with all CRIS reload_in_progress
augmented to include lra_in_progress.  I just noticed it when checking
because another port had a similar fix, where it mattered for LRA.

	* config/cris/constraints.md ("T"): Correct to
	define_memory_constraint.
---

diff --git a/gcc/config/cris/constraints.md b/gcc/config/cris/constraints.md
index 5efb61364f46..fa9aa19d13e3 100644
--- a/gcc/config/cris/constraints.md
+++ b/gcc/config/cris/constraints.md
@@ -100,7 +100,7 @@
 					       || reload_completed)")))
 
 ;; Extra constraints.
-(define_constraint "T"
+(define_memory_constraint "T"
   "Memory three-address operand."
   ;; All are indirect-memory:
   (and (match_code "mem")