diff options
| author | Hans-Peter Nilsson <hp@axis.com> | 2023-03-28 03:23:33 +0200 |
|---|---|---|
| committer | Hans-Peter Nilsson <hp@bitrange.com> | 2023-03-28 03:23:33 +0200 |
| commit | c4d61d3186b5f3db1f4823127ab11b5ff465a872 (patch) | |
| tree | 1a01be6afb8a6ddc7529e0611341e8a45f045ac9 | |
| parent | 09d0a1f33d910422b4674d8635b8b99bcb20ae5d (diff) | |
| download | gcc-c4d61d3186b5f3db1f4823127ab11b5ff465a872.zip gcc-c4d61d3186b5f3db1f4823127ab11b5ff465a872.tar.gz gcc-c4d61d3186b5f3db1f4823127ab11b5ff465a872.tar.bz2 | |
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.
| -rw-r--r-- | gcc/config/cris/constraints.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/config/cris/constraints.md b/gcc/config/cris/constraints.md index 5efb613..fa9aa19 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") |