Skip to content

R
riscv-gcc-1
Commit 26ba4aee by Jim Wilson
Options

(find_reloads, case 'o'): Accept a fully reloaded auto-increment address. 

From-SVN: r9168
parent 01188446
Showing with 8 additions and 0 deletions
gcc/reload.c
...@@ -2802,6 +2802,14 @@ find_reloads (insn, replace, ind_levels, live_known, reload_reg_p) ...@@ -2802,6 +2802,14 @@ find_reloads (insn, replace, ind_levels, live_known, reload_reg_p)
reject that case. */ reject that case. */
&& (ind_levels ? offsettable_memref_p (operand) && (ind_levels ? offsettable_memref_p (operand)
: offsettable_nonstrict_memref_p (operand))) : offsettable_nonstrict_memref_p (operand)))
/* A reloaded auto-increment address is offsettable,
because it is now just a simple register indirect. */
|| (GET_CODE (operand) == MEM
&& address_reloaded[i]
&& (GET_CODE (XEXP (operand, 0)) == PRE_INC
|| GET_CODE (XEXP (operand, 0)) == PRE_DEC
|| GET_CODE (XEXP (operand, 0)) == POST_INC
|| GET_CODE (XEXP (operand, 0)) == POST_DEC))
/* Certain mem addresses will become offsettable /* Certain mem addresses will become offsettable
after they themselves are reloaded. This is important; after they themselves are reloaded. This is important;
we don't want our own handling of unoffsettables we don't want our own handling of unoffsettables
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment