aboutsummaryrefslogtreecommitdiff
path: root/gcc
diff options
context:
space:
mode:
authorRichard Sandiford <richard.sandiford@arm.com>2023-02-13 21:13:59 +0000
committerRichard Sandiford <richard.sandiford@arm.com>2023-02-13 21:13:59 +0000
commit3cac06d84f334705ed0bce12fbc3a4cec4a8fd3b (patch)
tree6ccaabfdea739c4e58015ca06dad436957b8518b /gcc
parenta33e3dcbd15e73603796e30b5eeec11a0c8bacec (diff)
downloadgcc-3cac06d84f334705ed0bce12fbc3a4cec4a8fd3b.zip
gcc-3cac06d84f334705ed0bce12fbc3a4cec4a8fd3b.tar.gz
gcc-3cac06d84f334705ed0bce12fbc3a4cec4a8fd3b.tar.bz2
lra: Replace subregs in bare uses & clobbers [PR108681]
In this PR we had a write to one vector of a 4-vector tuple. The vector had mode V1DI, and the target doesn't provide V1DI moves, so this was converted into: (clobber (subreg:V1DI (reg/v:V4x1DI 92 [ b ]) 24)) followed by a DImode move. (The clobber isn't really necessary or helpful for a single word, but would be for wider moves.) The subreg in the clobber survived until after RA: (clobber (subreg:V1DI (reg/v:V4x1DI 34 v2 [orig:92 b ] [92]) 24)) IMO this isn't well-formed. If a subreg of a hard register simplifies to a hard register, it should be replaced by the hard register. If the subreg doesn't simplify, then target-independent code can't be sure which parts of the register are affected and which aren't. A clobber of such a subreg isn't useful and (again IMO) should just be removed. Conversely, a use of such a subreg is effectively a use of the whole inner register. LRA has code to simplify subregs of hard registers, but it didn't handle bare uses and clobbers. The patch extends it to do that. One question was whether the final_p argument to alter_subregs should be true or false. True is IMO dangerous, since it forces replacements that might not be valid from a dataflow perspective, and uses and clobbers only exist for dataflow. As said above, I think the correct way of handling a failed simplification would be to delete clobbers and replace uses of subregs with uses of the inner register. But I didn't want to write untested code to do that. In the PR, the clobber caused an infinite loop in DCE, because of a disagreement about what effect the clobber had. But for the reasons above, I think that was GIGO rather than a bug in DF or DCE. gcc/ PR rtl-optimization/108681 * lra-spills.cc (lra_final_code_change): Extend subreg replacement code to handle bare uses and clobbers. gcc/testsuite/ PR rtl-optimization/108681 * gcc.target/aarch64/pr108681.c: New test.
Diffstat (limited to 'gcc')
-rw-r--r--gcc/lra-spills.cc3
-rw-r--r--gcc/testsuite/gcc.target/aarch64/pr108681.c15
2 files changed, 18 insertions, 0 deletions
diff --git a/gcc/lra-spills.cc b/gcc/lra-spills.cc
index a8d7e60..4af85c4 100644
--- a/gcc/lra-spills.cc
+++ b/gcc/lra-spills.cc
@@ -860,6 +860,9 @@ lra_final_code_change (void)
lra_update_dup (id, i);
insn_change_p = true;
}
+ if ((GET_CODE (pat) == USE || GET_CODE (pat) == CLOBBER)
+ && alter_subregs (&XEXP (pat, 0), false))
+ insn_change_p = true;
if (insn_change_p)
lra_update_operator_dups (id);
diff --git a/gcc/testsuite/gcc.target/aarch64/pr108681.c b/gcc/testsuite/gcc.target/aarch64/pr108681.c
new file mode 100644
index 0000000..2391eaa
--- /dev/null
+++ b/gcc/testsuite/gcc.target/aarch64/pr108681.c
@@ -0,0 +1,15 @@
+/* { dg-options "-O" } */
+
+#pragma GCC aarch64 "arm_neon.h"
+typedef __Int64x1_t int64x1_t;
+void foo (int64x1x4_t);
+
+void
+bar (int64x1_t a)
+{
+ for (;;) {
+ int64x1x4_t b;
+ b.val[3] = a;
+ foo (b);
+ }
+}