aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRichard Sandiford <richard.sandiford@arm.com>2023-09-07 07:28:50 +0100
committerRichard Sandiford <richard.sandiford@arm.com>2023-09-07 07:28:50 +0100
commit10d59b802a7db9ae908291fb20627c1493cfa26c (patch)
tree5bba7807c49b9f07de13fdd9289ba63a8cd2815c
parent572abb52f5761a647035ee39d0e443c1c3622e75 (diff)
downloadgcc-10d59b802a7db9ae908291fb20627c1493cfa26c.zip
gcc-10d59b802a7db9ae908291fb20627c1493cfa26c.tar.gz
gcc-10d59b802a7db9ae908291fb20627c1493cfa26c.tar.bz2
lra: Avoid unfolded plus-0
While backporting another patch to an earlier release, I hit a situation in which lra_eliminate_regs_1 would eliminate an address to: (plus (reg:P R) (const_int 0)) This address compared not-equal to plain: (reg:P R) which caused an ICE in a later peephole2. (The ICE showed up in gfortran.fortran-torture/compile/pr80464.f90 on the branch but seems to be latent on trunk.) These unfolded PLUSes shouldn't occur in the insn stream, and later code in the same function tried to avoid them. gcc/ * lra-eliminations.cc (lra_eliminate_regs_1): Use simplify_gen_binary rather than gen_rtx_PLUS.
-rw-r--r--gcc/lra-eliminations.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/lra-eliminations.cc b/gcc/lra-eliminations.cc
index df613cd..4daaff1 100644
--- a/gcc/lra-eliminations.cc
+++ b/gcc/lra-eliminations.cc
@@ -406,7 +406,7 @@ lra_eliminate_regs_1 (rtx_insn *insn, rtx x, machine_mode mem_mode,
elimination_fp2sp_occured_p = true;
if (! update_p && ! full_p)
- return gen_rtx_PLUS (Pmode, to, XEXP (x, 1));
+ return simplify_gen_binary (PLUS, Pmode, to, XEXP (x, 1));
if (maybe_ne (update_sp_offset, 0))
offset = ep->to_rtx == stack_pointer_rtx ? update_sp_offset : 0;