Bin Cheng wrote: > In short, I think the confliction of reloads with type > RELOAD_FOR_INPADDR_ADDRESS > and type RELOAD_FOR_INPUT_ADDRESS should be handled in > "reload_reg_reaches_end_p". > Also I think RELOAD_FOR_OUTPUT_ADDRESS/RELOAD_FOR_OUTADDR_ADDRESS have the > issue > symmetrically, though I have no test case for it.
Yes, I agree with your reasoning here. This looks like an oversight. > PR target/52804 > * reload1.c (reload_reg_reaches_end_p): Check whether successor > reload with > type RELOAD_FOR_INPUT_ADDRESS kills reload register of current one > with type > RELOAD_FOR_INPADDR_ADDRESS. This is OK. (You also ought to mention the RELOAD_FOR_OUTADDR_ADDRESS part of the change in the ChangeLog.) Thanks, Ulrich -- Dr. Ulrich Weigand GNU Toolchain for Linux on System z and Cell BE ulrich.weig...@de.ibm.com
