| commit | c4d61d3186b5f3db1f4823127ab11b5ff465a872 | |
| author | Hans-Peter Nilsson <hp@axis.com> | |
| Tue, 28 Mar 2023 01:23:33 +0000 (28 03:23 +0200) | ||
| committer | Hans-Peter Nilsson <hp@bitrange.com> | |
| Tue, 28 Mar 2023 01:23:33 +0000 (28 03:23 +0200) | ||
| tree | 1a01be6afb8a6ddc7529e0611341e8a45f045ac9 | treesnapshot (tar.gz zip) |
| parent | 09d0a1f33d910422b4674d8635b8b99bcb20ae5d | commitdiff |
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.
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.
| gcc/config/cris/constraints.md | diffblobblamehistory |